Get access to the Accounts API
How to ask for the Accounts API, how we switch it on for your business, what the Accounts API card shows, what changes once it is on, and what happens if it is switched off.
Overview
The Accounts API reads your Vezmo accounts, so we switch it on one business at a time. You ask from the dashboard, and our
team looks at the request and switches it on. Until then, the API answers 403 with
the code api_access_not_enabled to every Accounts API call from your keys.
What the API reads is on the Accounts API page.
Ask for access
You need the API keys permissions to see the card. If you can't see it, ask whoever manages your team's roles. See Your team and roles.
Open the Accounts API card
Go to Settings, then Developers, and find Accounts API. It also sits under the keys in Payments › VezmoPay › Developers › API keys.
Select Ask for access
A support ticket opens with the subject Accounts API access. Tell us what you'll use it for, for example reconciling your accounts in your ERP, then send it.
Wait for our reply
We reply on the ticket. When the Accounts API is on, the card says On · read only.
What the card shows
| Card | What it means |
|---|---|
| Not on yet | The Accounts API isn't on for your business. The four reads are shown locked, with Ask for access. |
| On · read only | Your keys can be given the Accounts API permissions. The card shows Create a key and three steps to start. |
Once it is on
- New permissions in the key form. When you generate a key, a section called Accounts API · read only lists four permissions: accounts and balances, transactions, statements and account events. Before access they are shown as Not on yet and can't be ticked. See Keys and permissions for the Accounts API.
- Live keys before VezmoPay. Live keys normally open once VezmoPay is active for your business. With the Accounts API on, you can make a live key before that, holding only Accounts API permissions. The Live keys card says so.
- Accounts events for webhooks. Endpoints that use the Standard Webhooks format can listen to Accounts events. See Webhooks for Accounts.
Keys you made before keep the permissions they have. A key can't be given more later: make a new one with the Accounts API permissions.
If it is switched off
Our team can switch the Accounts API off for a business. From then on:
- every Accounts API call from your keys answers
403with the codeapi_access_not_enabled; - your keys keep their other permissions, so the rest of your integration goes on working;
- your webhook endpoints can still be edited: you can take Accounts events off them or change their URL, not add events;
- Accounts events stop being recorded for your business, and Accounts events still waiting to be delivered aren't sent. Test events still go.
Questions
Who can ask?
Anyone in your business who can see API keys. Our team looks at each request before switching it on.
Can I switch it on myself?
No. Only our team can switch it on or off.
Does asking change anything else?
No. Your accounts, keys and webhooks stay as they are until the Accounts API is on.
Related
Vezmo is a financial technology company, not a bank. Banking, stablecoin and card services are provided by regulated partners.
Facts checked against the product on 14 Nov 2026.
Was this page helpful?
Accounts API
Read your Vezmo accounts from your own systems, covering what the Accounts API reads (accounts, balances, transactions, statements and events), how a call is made, versions, amounts, paging, errors and limits, and what no key can ever do.
Keys and permissions for the Accounts API
The four Accounts API permissions and what each reads, choosing them when you generate a key, test and live keys, live keys before VezmoPay, the key ID and secret, getting an access token from POST /oauth/token, and what each refusal means.