---
title: "Get card's available spend limit"
method: GET
path: "/v1/cards/{card_token}/spend_limits"
tags: ["Card"]
---

# Get card's available spend limit

`GET /v1/cards/{card_token}/spend_limits`

Get a Card's available spend limit, which is based on the spend limit configured on the Card and the amount already spent over the spend limit's duration. For example, if the Card has a monthly spend limit of $1000 configured, and has spent $600 in the last month, the available spend limit returned would be $400.

## Path parameters

- `card_token` string, uuid, required

## Response `200`

OK

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

## 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.
- `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)