Only transaction fetches use credits
Reading accounts, transactions and balances, and linking an account, no longer use a credit.
With a live key, a credit is now used only by a transaction fetch: a call that fetches transactions from the bank. Everything else is free.
Uses one credit when it succeeds
Section titled “Uses one credit when it succeeds”POST /accounts/{id}/sync, however many bank accounts it ingests.POST /linkwithsyncTransactions: true. The credit is returned if the fetch fails.- A customer completing a link request or an access request.
Now free
Section titled “Now free”GET /accountsandGET /accounts/{id}.GET /accounts/{id}/transactionsandGET /accounts/{id}/balance. These read transactions Banklink already holds.POST /linkwithoutsyncTransactions, andPOST /link/otp.
Creating link and access requests, deleting credentials, /health and /auth/validate were already free. A failed call is never charged.
When the organisation has no credits, a billed call returns 402 insufficient_credits. POST /link with syncTransactions: true now does the same, instead of answering 200 with type: insufficient_credits. A link without syncTransactions no longer needs credits at all.
You don’t need to change anything. Polling accounts, transactions or balances no longer costs anything.