--- title: "Get account" method: GET path: "/v1/accounts/{account_token}" tags: ["Account"] --- # Get account `GET /v1/accounts/{account_token}` Get account configuration such as spend limits. ## Path parameters - `account_token` string, uuid, required ## Response `200` OK - AccountConfiguration - `account_holder` object - `business_account_token` string, required — Only applicable for customers using the KYC-Exempt workflow to enroll authorized users of businesses. Account_token of the enrolled business associated with an enrolled AUTHORIZED_USER individual. - `email` string, required — Email address. - `phone_number` string, required — Phone number of the individual. - `token` string, required — Globally unique identifier for the account holder. - `auth_rule_tokens` string[] — List of identifiers for the Auth Rule(s) that are applied on the account. This field is deprecated and will no longer be populated in the `account_holder` object. The key will be removed from the schema in a future release. Use the `/auth_rules` endpoints to fetch Auth Rule information instead. - `cardholder_currency` string — 3-character alphabetic ISO 4217 code for the currency of the cardholder. - `spend_limit` object, required — Spend limit information for the user containing the daily, monthly, and lifetime spend limit of the account. Any charges to a card owned by this account will be declined once their transaction volume has surpassed the value in the applicable time limit (rolling). A lifetime limit of 0 indicates that the lifetime limit feature is disabled. - `daily` integer, required — Daily spend limit (in cents). - `lifetime` integer, required — Total spend limit over account lifetime (in cents). - `monthly` integer, required — Monthly spend limit (in cents). - `state` 'ACTIVE' | 'PAUSED' | 'CLOSED', required — Account state: * `ACTIVE` - Account is able to transact and create new cards. * `PAUSED` - Account will not be able to transact or create new cards. It can be set back to `ACTIVE`. * `CLOSED` - Account will not be able to transact or create new cards. `CLOSED` accounts are unable to be transitioned to `ACTIVE` or `PAUSED` states. Accounts can be manually set to `CLOSED`, or this can be done by Lithic due to failure to pass KYB/KYC or for risk/compliance reasons. Please contact [support.lithic.com](https://support.lithic.com/) if you believe this was done by mistake. - `substatus` 'FRAUD_IDENTIFIED' | 'SUSPICIOUS_ACTIVITY' | 'RISK_VIOLATION' | 'END_USER_REQUEST' | 'ISSUER_REQUEST' | 'NOT_ACTIVE' | 'INTERNAL_REVIEW' | 'OTHER', nullable — Account state substatus values: * `FRAUD_IDENTIFIED` - The account has been recognized as being created or used with stolen or fabricated identity information, encompassing both true identity theft and synthetic identities. * `SUSPICIOUS_ACTIVITY` - The account has exhibited suspicious behavior, such as unauthorized access or fraudulent transactions, necessitating further investigation. * `RISK_VIOLATION` - The account has been involved in deliberate misuse by the legitimate account holder. Examples include disputing valid transactions without cause, falsely claiming non-receipt of goods, or engaging in intentional bust-out schemes to exploit account services. * `END_USER_REQUEST` - The account holder has voluntarily requested the closure of the account for personal reasons. This encompasses situations such as bankruptcy, other financial considerations, or the account holder's death. * `ISSUER_REQUEST` - The issuer has initiated the closure of the account due to business strategy, risk management, inactivity, product changes, regulatory concerns, or violations of terms and conditions. * `NOT_ACTIVE` - The account has not had any transactions or payment activity within a specified period. This status applies to accounts that are paused or closed due to inactivity. * `INTERNAL_REVIEW` - The account is temporarily paused pending further internal review. In future implementations, this status may prevent clients from activating the account via APIs until the review is completed. * `OTHER` - The reason for the account's current status does not fall into any of the above categories. A comment should be provided to specify the particular reason. - `comment` string — Additional context or information related to the account. - `token` string, uuid, required — Globally unique identifier for the account. This is the same as the account_token returned by the enroll endpoint. If using this parameter, do not include pagination. - `verification_address` object - `address1` string, required — Valid deliverable address (no PO boxes). - `address2` string — Unit or apartment number (if applicable). - `city` string, required — City name. - `country` string, required — Country name. Only USA is currently supported. - `postal_code` string, required — Valid postal code. Only USA postal codes (ZIP codes) are currently supported, entered as a five-digit postal code or nine-digit postal code (ZIP+4) using the format 12345-1234. - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format. - `created` string, date-time, nullable, required — Timestamp of when the account was created. ## Other responses - `400` — A parameter in the query given in the request does not match the valid queries for the endpoint. - `401` — | | | |---|---| | User has not been authenticated | Invalid or missing API key | | API key is not active | The API key used is no longer active | | Could not find API key | The API key provided is not associated with any user | | Please provide API key in Authorization header | The Authorization header is not in the request | | Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](https://lithic.com/contact) | | Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege | Reach out at [lithic.com/contact](https://lithic.com/contact) | - `404` — The specified resource was not found. - `422` — Unprocessable entity. - `429` — Client has exceeded the number of allowed requests in a given time period. | | | |---|---| | Rate limited, too many requests per second | User has exceeded their per second rate limit | | Rate limited, reached daily limit | User has exceeded their daily rate limit | | Rate limited, too many keys tried | One IP has queried too many different API keys | --- [API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)