Open Banking API

Name: Open Banking API API
Brand: Open Banking API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey54 EndpointsREST

For Agents

Programmatically create an account access consent, retrieve an account access consent. Covers 54 operations with apiKey authentication.

Connect the Open Banking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Banking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Open Banking API API.

Create an account access consent

Retrieve an account access consent

Delete an account access consent

Query and filter Open Banking API records by parameters

GET STARTED

Start building with Open Banking API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Open Banking API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Open Banking API API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'create an account access consent', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

54 endpoints — the revolut open banking api is the gateway for third-party providers to interact with revolut customers and products.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Open Banking API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create an account access consent') and Jentic returns the matching Open Banking API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Open Banking API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Open Banking API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.