Skip to main content


Welcome to the Unit API! Our documentation will walk you from the basics (authentication, request structure) to using and creating financial products (accounts, cards, payments etc.).

Unit treats each client as a standalone organization. You may log into the Unit Dashboard to manage your organization's API tokens, users, applications, customers, accounts and more.

Ready to get started? Sign up here to receive immediate access to our Sandbox and start building with Unit.

The introduction covers basic concepts you should be familiar with in order to make the most out of the platform.

Bank Partners

Unit has currently supports nine bank partners, offering various products (lending & banking) to a range of end customers (individuals, sole proprietors and businesses). As our network of bank partners continues to grow we will offer even more options.

While the majority of features are accessible across all our bank partners, it's important to note that there are certain features that are not currently available on all of them. In such cases, the documentation will clearly indicate so.


Our API and Dashboard are available in two environments:

NameDashboard URLAPI URL

The sandbox environment contains special API operations that allow you to easily test and simulate different activities, from incoming payments to card spend. You can find the full reference under the various Simulation pages.


Unit, with the help of our developer community, maintains open source SDKs in multiple programming languages. The SDKs are available on Github, and encapsulate all resources and API endpoints.

Java (beta)Unit

API Coverage

The SDKs are updated asynchronously, once new capabilities are built into the API. Note that the SDKs are open source, and you may update them if you need a certain API endpoint that isn't currently covered. Otherwise, you may reach out to us and we will make an effort to accommodate your request.

OpenAPI Specification

OpenAPI is an industry standard for describing RESTful APIs, which can be used to provide easier use and integration with the API, the generation of client libraries (SDKs), testing, integration with various developer tools and more. An OpenAPI 3.0 specification for the Unit API is available here.

You may use the Unit OpenAPI specification along with Swagger or the OpenAPI generators to auto-generate Unit API client libraries for your language of choice.

Note that we do not guarantee that the generated SDKs will be fully compatible with our API, nor support all endpoints. We encourage members of the Unit SDKs community to share feedback, bug reports and pull requests with suggestions for improvements to help us identify and address any potential issues.

Reporting Issues

You may report any issues you find with the SDK by creating a Github issue (TypeScript issues, Python issues). As previously mentioned, the SDKs are open source, so if you have resolved an issue locally, please raise a PR and we will publish it, so that other members of the Unit developer community may benefit from it.

Postman Collection

You can interact immediately with the Unit API via Postman in two ways.

1) Make API calls yourself. To get started, import the Unit API Postman Collection into Postman. You can then send any request with the dummy data provided or customize it.

2) Populate your development environment with a dummy data set. You can import the Unit API Starter Collection into Postman, then run the full collection.

After making requests with Postman, you can see the API calls you made reflected in the Unit Dashboard as applications, customers, accounts, transactions, etc.

Both collections contain two variables:

tokenYour API Token. You can create it from the API Tokens page in the Developer section of the Unit Dashboard.
server_urlInitially set to the Unit Sandbox environment (

For more information, see the following Postman article: Importing Data into Postman.

JSON Schema

You can download an archive with JSON Schemas for the Unit API.

You can use one of the libraries that generate types from JSON schemas - see table below for examples of common language specific libraries.

NodeJS / TypeScriptjson-schema-to-typescript
Pythonyacg (Yet Another Code Generation)


Unit's API uses OAuth 2.0 Bearer Token to authenticate requests. All API calls must include a bearer token.


An invalid, missing or expired token will result in HTTP 401 Unauthorized responses.

GET /accounts HTTP/1.1
Authorization: Bearer v2.public.eyJyb2xlIjoib3JnIiwidX...


Unit Clients can use 2 types of API tokens:

  • Org API tokens are broad, system level API tokens, that are not restricted to a specific end customer.
  • Customer Tokens are end-customer specific, and only allow access to resources associated with a specific customer.

When a token is created, it is assigned a set of Scopes The scopes define the resources that can be accessed using that token, and the access level (read / write) that will be allowed using that token.


Unit recommends using Customer Tokens as a default, for all end-customer related actions:

  • Customer tokens deny access to all resources that aren't associated with the authenticated customer. If a customer token with access to sensitive scopes is compromised, the impact is restricted to the specific customer. If an org API token with access to sensitive scopes is compromised, the impact could be far greater.
  • Customer tokens include built-in Two Factor Authentication (OTP) and expiry (customizable, up to 24 hours), so you don't have to implement it.
In order to retrieve decoded token information, send an HTTP GET request to the /identity endpoint with the Authorization header containing the token.
curl -X GET '' \
-H "Authorization: Bearer ${TOKEN}"

Two Factor Authentication (2FA)

Unit requires that you take the customer through two factor authentication in a number of scenarios, detailed in the table below.

Use caseDetails
ApplicationsThe customer's phone number must be verified using OTP (which is a form of 2FA) In order to submit an application. If you choose to use Unit's application form, we will execute the 2FA on your behalf.
Sensitive ScopesThe customer must be taken through 2FA at least once in the 24 hours prior to accessing a sensitive scope. We highly recommend using customer tokens for that purpose.
PCI Sensitive dataYou are required to use a valid Unit customer token in order to access and execute actions that are covered by PCI compliance (card related data and actions, including activating the card, setting and changing the PIN, and revealing the card number and CVV2 for virtual cards). You cannot rely on your own two factor authentication and Org API tokens for that purpose, unless you are PCI level 1 compliant.

If you would like to rely on your own two factor authentication for all non-PCI related sensitive actions, you may do so. In this scenario, you would use an Org API token with the relevant scopes to access the Unit API.

Acceptable two factor authentication methods include one time password (OTP) (through SMS or call), biometric authentication and other industry recognizable methods.

A successful two factor authentication is valid for up to 24 hours, and you responsible for enforcing the 24 hour expiry and re-authenticating the customer when needed.


Scopes define the level of access a token will have to resources in Unit.

A list of all scopes within Unit:


Scopes that are related to fund movement are considered sensitive, and are in the table below. Scopes that require PCI compliance to access are highlighted in .

Any action that requires access to these scopes, must be protected by Two Factor Authentication. If you follow the best practice and use a Customer Token for such actions, Unit will execute the authentication for you. If you decide to use an Org Token, you will have to implement it yourself.

The org token can be used without 2FA for sensitive operations triggered from the server side.

ResourceRead ScopeWrite ScopeAccessible Using
ApplicationapplicationsOrg API token
Customer Tokencustomer-tokenOrg API token
CustomerscustomersOrg API token, Customer Token
Customer Tags--Org API token, Customer Token
AccountsaccountsOrg API token, Customer Token (exception: Close Account )
CardscardsOrg API token, Customer Token
Cards SensitiveCustomer Token
TransactionstransactionsOrg API token, Customer Token
Authorizationsauthorizations--Org API token, Customer Token
Statementsstatements--Org API token, Customer Token
PaymentspaymentsOrg API token, Customer Token
Payments to a counterparty--Org API token, Customer Token
Payments to a linked account--Org API token, Customer Token
Payments ACH Debit--Org API token, Customer Token
Payments ACH--Org API token, Customer Token
Payments Wire--Org API token, Customer Token
CounterpartiescounterpartiesOrg API token, Customer Token
EventseventsOrg API token, Customer Token
WebhookswebhooksOrg API token
Authorization Requestsauthorization-requestsOrg API token
Batch Releasesbatch-releasesOrg API token
Check Depositscheck-depositscheck-deposits-writeOrg API token, Customer Token
Check Paymentscheck-paymentsOrg API token, Customer Token
Account End-Of-Dayaccounts--Org API token, Customer Token
Received Paymentreceived-paymentsOrg API token
ChargebackchargebacksOrg API token
RewardrewardsOrg API token

By default, creating an Org API token through the Create Token Page on the Dashboard selects the recommended scopes for an Org API token.

Required Fields

Unless specified otherwise, all the fields in the request payload are required. Some fields are only required under specific circumstances - these fields are pointed out throughout the documentation.

Retrying API Requests

API requests can fail for many reasons, from network components failures, API rate limits, timeouts or service incidents. As a best practice, we recommend implementing a request retrying mechanism with the following attributes:

  1. Only the requests that failed with the following HTTP status codes should be retried:
    • 5xx (Server errors)
    • 429 (Rate Limits)
    • 408 (Timeouts)
  2. Retry should have an exponential backoff and/or jitter.
  3. Make sure to add idempotency key where applicable.

Rate Limits

Our rate limit is based on your IP address and is set to 1,000 requests per minute. The limit applies to each environment (sandbox and live) separately. If the limit is exceeded, responses will include an HTTP 429 status code along with a relevant message.


All of our APIs have timeouts to make sure we fail as soon as possible and allow you to retry the request. It is considered good practice to set the same request timeout for the clients as well. We have two types of timeouts:

  • Short timeout - Most APIs will use the default timeout of 5 seconds
  • Long timeout - Few APIs require longer timeouts, these use a timeout of 60-120 seconds

Please refer to the relevant API docs to determine the timeout for your request.


To help you manage, categorize and enrich resources, Unit allows you to attach your own metadata to them in the form of tags (key-value pairs). Common examples:

  • Attaching a my_customer_id tag to an application with a value that helps you connect the application to a unique customer identifier in your app.
  • Attaching a purpose tag to an account with a value such as tax, saving or checking.
"data": {
"type": "depositAccount",
"attributes": {
/// ...
"tags": {
"purpose": "tax",
"my_account_id": "b6f395c9-e58a-40a5-a5a4-901d603440b9"
/// ...

Tag Inheritance

Some resources are created as a result of you creating a parent resource (customer and application respectively). They therefore inherit all tags from their parent resource, as specified in the table below.

Tag Support

Resource TypeTag SupportInherited From
Application FormsYes
AuthorizationsYesAuthorization Request
Authorization RequestsYes
Check DepositsYes
Deposit AccountsYes
Credit AccountsYes
TransactionsYesPayment, Authorization Request

Searching by Tags

The List operation under certain resources (such as Application, Customer or Payment) supports searching by tags. You can search by passing any number of key-value pairs. The response will include the resources whose tags contain the key-value pairs you specified, based on the principles of JSON containment.

Example uses:

  • Assume you attach 5 different tags to all applications you create on Unit. One of these tags is a my_customer_id tag that helps you connect every Unit application to a unique customer identifier in your app. To search for the application that belongs to a known customer, specify a key-value pair in the following way: { "my_customer_id": "b6f395c9-e58a-40a5-a5a4-901d603440b9" }
  • Assume you attach 4 different tags to all book transfers you create on Unit. Two of these tags are is_loan and number_of_repayments. To search for all loans that have four repayments, specify two key-value pairs in the following way: { "is_loan": "true", "number_of_repayments": "4" }

Updating Tags

You can add, update or delete tags from resources with the tags attribute on their corresponding Update operation (for example, Update Deposit Account).

Unit follows the JSON Merge Patch RFC when updating the tags. In general:

  • To add or update a tag, specify its key and value.
  • To delete a tag, specify its key and null for the value.

Tag Constraints

  • Maximum number of tags per resource: 15
  • Keys and values are case-sensitive
  • Key constraints: 128 characters consisting of letters, numbers and underscores
  • Value constraints: 256 characters

The List operation under certain resources (such as Application, Customer or Transaction) supports full-text search, to help you find the desired resources more easily.

In particular, you can use full-text search to quickly build better end-customer experiences. An example would be adding a search box that lets end-customers search for transactions by merchant name (e.g. 'starbucks') when browsing transactions under their account.

Full-Text search rules:

  • unquoted text: text without quote marks will be converted into words separated by 'And' operators. Example: 'john doe' will search for a resource with the value 'john' and the value 'doe'.

  • OR: will be converted into words separated by the 'Or' operator. Example: 'john or doe' will search for a resource with either the value 'john' or the value 'doe'.

  • -: will be converted into the 'Not' operator. Example: 'john -doe' will search for a resource with the value 'john' and without the value 'doe'.


List operations on all resources (example: List Customers) return a list of resources.

To page through a long list, use the following two query parameters:

  • page[limit]: Limit the number of resources to be returned (between 1 and 1000). Defaults to 100 when no value is provided.
  • page[offset]: Number of resources to skip. Defaults to 0 when no value is provided.


Some of our API operations support request idempotency, allowing you to call a sensitive operation multiple times and assume that its work will be done no more than once. You may use any string of up to 255 characters as an idempotency key (we recommend UUID version 4).

The guarantee of idempotency is crucial when an API call has failed without a clear reason and a retry is due. For example, if creating a payment does not succeed due to a network error, you can safely retry creating the payment, passing the same idempotency key and assume the payment will occur no more than once, regardless of the number of calls.

Idempotency keys are guaranteed effective for 48 hours from the time they're used successfully. After this time window, they will be recycled and existing keys will therefore be treated as new.


Idempotency keys are not shared between different API operations, so you could potentially use the same idempotency key for different types of operations, although we do not recommended it.

One exception here is debit card creation for which both physical card creation and virtual card creation are sharing the idempotency key.

Organization Accounts

Organization accounts (also known as org accounts) are special-purpose accounts that Unit sets up to support your activities. Unlike deposit accounts, org accounts exist on the org level and are not under your customers. Since the accounts have a special purpose, they only support specific functions that are relevant to their use case.

Common types of org accounts include:

  • Revenue account: the account that Unit automatically credits with your org's interchange, interest and payment revenues. Withdrawals from the Revenue account will be done to an account of your choice after it is linked with your revenue account. Contact Unit support to set up a link to your chosen account/s.
  • Reserve account: the account that Unit automatically debits for a range of situations, including disputes and ACH returns. This account requires an initial balance to be funded, and monthly recalculation to determine the reserve amount required based on risk.
  • Batch account: see Batch Payments

Your org accounts can be accessed from the Unit Dashboard.


Some types of organization accounts, such as batch accounts, are designed to be used for incoming and outgoing payments. Others, such as reserve accounts, offer limited payments functionality by design.

Data Integrations

Unit allows its clients access to their raw data, so that they can build their own reporting solutions and make informed business decisions. This integration provides a daily upload into an AWS S3 or Google Cloud Storage bucket. You can pull the data into your own data warehouse easily with existing cloud storage connectors, eliminating the need to build a sequence of API calls to obtain data. For more information visit the AWS S3 guide or GCS guide


We publish a monthly review of all the newest updates and features added to the platform on our Changelog. Subscribe to our newsletter to receive monthly updates on platform and product changes, directly to your inbox.


Unit will, from time to time, deprecate certain API endpoints and services. This does not mean that they are no longer available - deprecating an endpoint means that this is no longer the recommended way to implement the relevant functionality, and Unit will not make updates or changes to that endpoint. Deprecated endpoints may be retired at a later point in time - subject to a minimum of a six month notice period, like all breaking changes on Unit, unless they follow an urgent security or compliance change.


Check out our continuously updating public Roadmap to see what's planned for the coming months.