---
title: "Get account's available spend limits"
method: GET
path: "/v1/accounts/{account_token}/spend_limits"
tags: ["Account"]
---

# Get account's available spend limits

`GET /v1/accounts/{account_token}/spend_limits`

Get an Account's available spend limits, which is based on the spend limit configured on the Account and the amount already spent over the spend limit's duration. For example, if the Account has a daily spend limit of $1000 configured, and has spent $600 in the last 24 hours, the available spend limit returned would be $400.

## Path parameters

- `account_token` string, uuid, required

## Response `200`

OK

- AccountSpendLimits
  - `available_spend_limit` object, required
    - `daily` integer — The available spend limit (in cents) relative to the daily limit configured on the Account (e.g. 100000 would be a $1,000 limit).
    - `lifetime` integer — The available spend limit (in cents) relative to the lifetime limit configured on the Account.
    - `monthly` integer — The available spend limit (in cents) relative to the monthly limit configured on the Account.
  - `spend_limit` object
    - `daily` integer — The configured daily spend limit (in cents) on the Account.
    - `lifetime` integer — The configured lifetime spend limit (in cents) on the Account.
    - `monthly` integer — The configured monthly spend limit (in cents) on the Account.
  - `spend_velocity` object
    - `daily` integer — Current daily spend velocity (in cents) on the Account. Present if daily spend limit is set.
    - `lifetime` integer — Current lifetime spend velocity (in cents) on the Account. Present if lifetime spend limit is set.
    - `monthly` integer — Current monthly spend velocity (in cents) on the Account. Present if monthly spend limit is set.

## Other responses

- `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.
- `409` — Client is not authorized to call the endpoint
- `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)