canonical: https://jentic.com/apis/revolut.com/open-banking-api # Revolut Open Banking API The Revolut Open Banking API is the gateway for third-party providers to interact with Revolut customers and products. You can take advantage of the Open Banking API to build your banking applications whether you are: - A regulated third party provider that wants to get account and transaction information of Revolut customers and initiate different types of payments, or - An innovative service pro. The API exposes 54 endpoints secured with apiKey authentication. ## For AI agents Programmatically create an account access consent, retrieve an account access consent. Covers 54 operations with apiKey authentication. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Create an account access consent - Retrieve an account access consent - Delete an account access consent - Query and filter Open Banking API records by parameters - Monitor Open Banking API operational status and events ## Use cases ### Payments Operations Use the Open Banking API to perform payments operations programmatically. The API provides 54 endpoints covering core functionality including create an account access consent, retrieve an account access consent, delete an account access consent. Example prompt: Call POST /account-access-consents to create an account access consent ### Automated Applications Management Automate applications operations by combining multiple Open Banking API endpoints. Agents can retrieve an account access consent and then delete an account access consent in a single workflow. Example prompt: Call GET /account-access-consents/{ConsentId} to retrieve an account access consent, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Open Banking API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'create an account access consent', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /account-access-consents | Create an account access consent | | GET | /account-access-consents/{ConsentId} | Retrieve an account access consent | | DELETE | /account-access-consents/{ConsentId} | Delete an account access consent | | GET | /accounts | Retrieve all accounts | | GET | /accounts/{AccountId} | Retrieve an account | | GET | /accounts/{AccountId}/balances | Retrieve an account balance | | GET | /accounts/{AccountId}/beneficiaries | Retrieve all account's beneficiaries | | GET | /accounts/{AccountId}/direct-debits | Retrieve all account's direct debits | ## Key resources - **Applications** — These endpoints let you manage your applications. Applications can also be created in the [Develope - **Accounts** — Open Banking Accounts API is implemented as specified in the [Open Banking API documentation: Accoun - **Transactions** — Open Banking Transactions API is implemented as specified in the [Open Banking API documentation: Ac - **Domestic payment** — *Domestic payments*, which you can use for local payments in the local currency of the user. A domes - **Domestic scheduled payment** — *Domestic payments*, which you can use for local payments in the local currency of the user. A domes ## Why Jentic - **Setup:** Wiring the Revolut Open Banking API by hand means handling its Authorization header credential alongside the x-jws-signature it requires, choosing the live oba-auth.revolut.com or sandbox host, and managing retries yourself. Through Jentic you install once, import the Open Banking API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Open Banking puts the account id in the URL path (/accounts/{AccountId}), so a rule can pin your agent to one account: it can read that account's balances, beneficiaries, and direct debits and nothing else. You choose the operations it may call, so ones like deleting an account-access consent are not included unless you add them. - **Credential handling:** Your Revolut Open Banking credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an account access consent' or 'get account balances', and Jentic returns the matching Open Banking API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### What authentication does the Open Banking API use? The Open Banking API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I create an account access consent with the Open Banking API? Yes. Use the POST /account-access-consents endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Open Banking API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I create an account access consent through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an account access consent'. Jentic returns the matching Open Banking API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Open Banking API have? The Open Banking API exposes 54 endpoints covering applications, accounts, transactions operations. ### Can I limit what my agent is allowed to do with the Revolut Open Banking API? Yes. Because you run Jentic One yourself, you decide which Open Banking operations your agent may call and which credential it uses, so you can grant read calls like GET /accounts/{AccountId}/balances, /beneficiaries, and /direct-debits while withholding others. Since the account id sits in the URL path, your rules can pin the agent to a single account and let it read only that account's data. Operations such as DELETE /account-access-consents/{ConsentId} stay off limits unless you explicitly add them.