> ## Documentation Index
> Fetch the complete documentation index at: https://docs.imprint.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Get customer's account

> Returns the servicing snapshot for one of a customer's card accounts:
account status, credit limit and available credit, the amounts they owe,
the statement due date, and the APR.

Every amount is a positive integer in the smallest currency unit and
represents what the customer owes. A customer who owes nothing — or who
is in credit — reads as `0` rather than a negative number.

Per-statement figures — the statement balance, the minimum due, and
interest — are not on this response. Read them from the statements API.

`as_of` is when the snapshot was calculated, which is when the request
was served. It is the instant the figures were true, and what a cached
copy should be labelled with.

A secured account whose security deposit has not been funded reads as
`PENDING_FUNDING` and carries status and `as_of` alone: it has no credit
line yet, so there is no credit limit, balance, due date or APR to
report. This endpoint answers whether the account is usable now, not
where the application got to — the deposit amount, the offer terms and
the deadline to fund by are on `GET /v2/applications/{application_id}`,
whose `product_offers[].result` is `ACCEPTED_PENDING_ACTION` for the
same account.

**Required scope:** `ACCOUNT_READ`




## OpenAPI

````yaml /api-reference/2025-05-05/openapi.yaml get /v2/customers/{customer_id}/accounts/{account_id}
openapi: 3.1.0
info:
  title: Public Imprint API
  version: '2.0'
servers:
  - url: https://dev.sbx.imprint.co
    description: Imprint public api sandbox
security:
  - basicAuth: []
  - bearerAuth: []
paths:
  /v2/customers/{customer_id}/accounts/{account_id}:
    get:
      tags:
        - Customers
      summary: Get customer's account
      description: |
        Returns the servicing snapshot for one of a customer's card accounts:
        account status, credit limit and available credit, the amounts they owe,
        the statement due date, and the APR.

        Every amount is a positive integer in the smallest currency unit and
        represents what the customer owes. A customer who owes nothing — or who
        is in credit — reads as `0` rather than a negative number.

        Per-statement figures — the statement balance, the minimum due, and
        interest — are not on this response. Read them from the statements API.

        `as_of` is when the snapshot was calculated, which is when the request
        was served. It is the instant the figures were true, and what a cached
        copy should be labelled with.

        A secured account whose security deposit has not been funded reads as
        `PENDING_FUNDING` and carries status and `as_of` alone: it has no credit
        line yet, so there is no credit limit, balance, due date or APR to
        report. This endpoint answers whether the account is usable now, not
        where the application got to — the deposit amount, the offer terms and
        the deadline to fund by are on `GET /v2/applications/{application_id}`,
        whose `product_offers[].result` is `ACCEPTED_PENDING_ACTION` for the
        same account.

        **Required scope:** `ACCOUNT_READ`
      operationId: getAccount
      parameters:
        - $ref: '#/components/parameters/customerIdParam'
          name: customer_id
          in: path
        - $ref: '#/components/parameters/accountIdParam'
          name: account_id
          in: path
      responses:
        '200':
          description: Customer account
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Account'
        '403':
          description: API key is missing the required `ACCOUNT_READ` scope
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '404':
          description: >
            The customer was not found, or the account does not belong to them.

            `type` distinguishes the two: `CUSTOMER_NOT_FOUND_ERROR` means we
            hold

            no record of the customer, `ACCOUNT_NOT_FOUND_ERROR` means the

            `account_id` is not one of theirs.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomerNotFoundError'
components:
  parameters:
    customerIdParam:
      name: customer_id
      in: path
      required: true
      description: The unique identifier for the Imprint customer
      schema:
        type: string
        example: 2EE24580-B97B-4949-A65C-929CCB9B9B8D
    accountIdParam:
      name: account_id
      in: path
      required: true
      description: The unique identifier for the account, as returned by list accounts
      schema:
        type: string
        example: 7C1F9A34-2D6B-4E58-8A03-B15E7D9C4620
  schemas:
    Account:
      type: object
      description: |
        A customer's card account as of now. Amounts are integers in the
        smallest currency unit and are always positive: they say what the
        customer owes, so a paid-off or in-credit account reads as `0`.

        Per-statement figures live in the statements API, not here.
      required:
        - customer_id
        - account_id
        - status
        - as_of
      properties:
        customer_id:
          type: string
          description: The unique identifier for the customer
          example: 2EE24580-B97B-4949-A65C-929CCB9B9B8D
        account_id:
          type: string
          description: The unique identifier for the account
          example: 7C1F9A34-2D6B-4E58-8A03-B15E7D9C4620
        status:
          $ref: '#/components/schemas/AccountStatus'
        currency:
          $ref: '#/components/schemas/TransactionCurrency'
        credit_limit:
          $ref: '#/components/schemas/CurrencyAmount'
        available_credit:
          $ref: '#/components/schemas/CurrencyAmount'
        current_balance:
          allOf:
            - $ref: '#/components/schemas/CurrencyAmount'
          description: |
            Everything posted to the account, including activity since the last
            statement closed.
        overdue_amount:
          allOf:
            - $ref: '#/components/schemas/CurrencyAmount'
          description: >
            The amount past due — a minimum payment that was not made by its due

            date and is still outstanding. Unlike the minimum due, this moves

            during the cycle: a payment brings it down. `0` on an account that
            is

            current.
        statement_due_date:
          type: string
          description: |
            RFC-3339 timestamp when payment for the most recently closed
            statement is due. Absent on an account still in its first billing
            cycle, which has no closed statement yet.
          example: '2026-06-15T00:00:00Z'
        apr_percentage:
          type: number
          description: The purchase APR as a percentage
          example: 24.99
        as_of:
          type: string
          description: |
            RFC-3339 timestamp of when this snapshot was calculated, which is
            when the request was served. Balances move continuously — a purchase
            or a payment lands between one read and the next — so this is the
            instant the figures above were true. Use it to label or expire a
            cached copy, and to order two reads of the same account.
          example: '2026-08-27T14:22:31Z'
    ApiError:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - type
            - message
          properties:
            type:
              type: string
              description: The category of error being returned
              example: BAD_REQUEST_ERROR
            message:
              type: string
              description: A message describing the cause of the error
              example: 'unsupported reward_type: INVALID, must be STATEMENT or DELAYED'
    CustomerNotFoundError:
      type: object
      required:
        - type
        - message
      properties:
        type:
          type: string
          description: The category of error being returned
          example: CUSTOMER_NOT_FOUND_ERROR
        message:
          type: string
          description: A message describing the cause of the error
          example: 'Customer not found for provided ID: CSMR-v1-123'
        param:
          type: string
          description: The param causing the error
          example: customer_id
    AccountStatus:
      type: string
      description: |
        The lifecycle state of a customer's card account.

        Two states mean "approved but not usable yet", and they are distinct:

        - `PENDING_FUNDING` is a secured account whose security deposit has not
          been funded. The deposit is either still owed or a submitted payment
          is settling, so no card has been issued and the account cannot be
          spent on. It has no credit limit, balance or APR yet.
        - `INACTIVE` is an approved account whose card has not been activated
          yet — for a secured account, one whose deposit has already settled.

        `PENDING_FUNDING` only ever appears on a secured-credit-card product.
      enum:
        - OPEN
        - INACTIVE
        - PENDING_FUNDING
        - CLOSED
        - REVOKED
        - CHARGE_OFF
        - SOLD
      example: OPEN
    TransactionCurrency:
      type: string
      description: >-
        The 3-character currency code of the amount in ISO 4217 format (e.g.,
        "USD")
      example: USD
    CurrencyAmount:
      type: integer
      description: Amount in the smallest currency unit (e.g., cents for USD)
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: >-
        Basic HTTP authentication. Allowed headers-- Authorization: Basic
        <base64(api_key_id:api_key_secret)>
    bearerAuth:
      bearerFormat: auth-scheme
      description: >-
        Bearer HTTP authentication. Allowed headers-- Authorization: Bearer
        <api_key>
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.