---
title: "Update account credit configuration"
method: PATCH
path: "/v1/financial_accounts/{financial_account_token}/credit_configuration"
tags: ["Financial Account"]
---

# Update account credit configuration

`PATCH /v1/financial_accounts/{financial_account_token}/credit_configuration`

Update an account's credit configuration

## Path parameters

- `financial_account_token` string, uuid, required

## Request body

- FinancialAccountCreditConfigRequest
  - `credit_limit` integer
  - `external_bank_account_token` string, uuid
  - `credit_product_token` string — Globally unique identifier for the credit product
  - `tier` string — Tier to assign to a financial account
  - `auto_collection_configuration` AutoCollectionConfigurationRequest
    - `auto_collection_enabled` boolean — If auto collection is enabled for this account

## Response `200`

OK

- FinancialAccountCreditConfigResponse
  - `account_token` string, uuid, required — Globally unique identifier for the account
  - `credit_limit` integer, nullable, required
  - `external_bank_account_token` string, uuid, nullable, required
  - `credit_product_token` string, nullable, required — Globally unique identifier for the credit product
  - `tier` string, nullable, required — Tier assigned to the financial account
  - `auto_collection_configuration` AutoCollectionConfigurationResponse, required
    - `auto_collection_enabled` boolean, required — If auto collection is enabled for this account

## 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 |

## Changes

- **2026-07-20** `7732c7d99b3e` — 5 info
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `404`
  - added the non-success response with the status `422`
  - …1 more

[Change history](https://skmtc.dev/lithic-com/apis/lithic-developer-api/changes/v1/financial_accounts/:financial_account_token/credit_configuration/patch.md)

---

[API](https://skmtc.dev/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.dev/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/c9806df29604/schema)