---
title: "List funding sources"
method: GET
path: "/funding_sources"
tags: ["Funding"]
---

# List funding sources

`GET /funding_sources`

List all the funding sources associated with the Privacy account.

## Query parameters

- `account_token` string, uuid

## Response `200`

OK

- object
  - `data` FundingAccount[]
    - `account_name` string — Account name identifying the funding source. This may be `null`.
    - `created` string, date-time, required — An ISO 8601 string representing when this funding source was added to the Privacy account. This may be `null`. UTC time zone.
    - `last_four` string, required — The last 4 digits of the account (e.g. bank account, debit card) associated with this FundingAccount. This may be null.
    - `nickname` string — The nickname given to the `FundingAccount` or `null` if it has no nickname.
    - `state` 'ENABLED' | 'PENDING', required — State of funding source. Funding source states: * `ENABLED` - The funding account is available to use for card creation and transactions. * `PENDING` - The funding account is still being verified e.g. bank micro-deposits verification.
    - `token` string, uuid, required — A globally unique identifier for this FundingAccount.
    - `type` 'DEPOSITORY_CHECKING' | 'DEPOSITORY_SAVINGS', required — Types of funding source: * `DEPOSITORY_CHECKING` - Bank checking account. * `DEPOSITORY_SAVINGS` - Bank savings account.
  - `page` integer — Page number. Will always be 1.
  - `total_entries` integer — Total number of entries.
  - `total_pages` integer — Total number of pages. Will always be 1.

## 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 [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Please contact [api@privacy.com](mailto:api@privacy.com) | | Insufficient privileges to create unlocked cards. | Creating unlocked cards requires an additional privilege | Please contact [api@privacy.com](mailto:api@privacy.com) |
- `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.dev/privacy/apis/privacy-developer-api.md) · [All operations](https://skmtc.dev/privacy/apis/privacy-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/privacy/privacy-developer-api/revisions/85ef2cf28e6b/schema)