Enable Banking API

Name: Enable Banking API
Brand: Enable Banking API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer14 EndpointsREST

For Agents

Aggregate access to European bank accounts via PSD2 — start authorization sessions, read balances and transactions, and initiate payments.

Install Jentic One Beta

Connect the Enable Banking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Enable 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Enable Banking API.

Start a PSD2 authorization session for a chosen ASPSP and obtain the redirect for user consent

Authorize an active user session and persist it for subsequent calls

Retrieve account details, balances, and transactions across consented accounts

GET STARTED

Start building with Enable Banking API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Enable Banking API, keeping it validated and agent-ready. Enable Banking is an open banking aggregator that exposes a single PSD2-compliant API across European banks, covering authorization sessions, account information, balances, transactions, and payment initiation. The API handles the consent and session lifecycle so applications can read account data and initiate payments without integrating each bank individually. Use it for personal finance, accounting automation, and bill-pay products targeting the European market.

Use Cases

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

★ Personal Finance Aggregation

Connect users' European bank accounts via PSD2 consent and pull balances and transactions into a personal finance app. The API handles authorization session creation, ASPSP selection, and the per-account transactions endpoint, so the app integrates one API rather than each bank individually. Product teams use this to build account aggregation features without becoming a regulated entity themselves.

POST /auth and POST /sessions to obtain a session, then GET /accounts/{account_id}/transactions for each account the user has consented to.

Accounting Automation

Pull bank transactions into accounting software so invoices and expenses can be reconciled automatically. The API exposes balances and transactions per account, with the session lifecycle handled by /sessions endpoints. Finance operations teams use this to keep the books reconciled in near real time rather than waiting for monthly statement uploads.

Call GET /accounts/{account_id}/balances and GET /accounts/{account_id}/transactions and post the results to the accounting system as journal entries.

Account-to-Account Payment Initiation

Initiate account-to-account payments directly from a user's bank without going through a card network. The API exposes POST /payments to create the payment, GET /payments/{payment_id} to check status, and DELETE /payments/{payment_id} to cancel before settlement. E-commerce and bill-pay products use this to reduce processing fees and offer direct bank checkout in Europe.

POST /payments with the debtor account, creditor account, and amount, then poll GET /payments/{payment_id} until status reaches a terminal state.

Agent-Driven Bank Linking

An agent in a financial assistant flow walks the user through bank selection, starts the authorization, and once consent returns reads accounts and transactions to produce a spending summary. Through Jentic the agent searches by intent, loads the schemas, and chains calls without bespoke client code. Linking a new account drops from a multi-step custom flow to a single agent task.

Search Jentic for 'connect a European bank account', execute GET /aspsps to list banks, POST /auth, POST /sessions, and GET /accounts/{account_id}/transactions, then summarise the last 30 days of spending.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for enable banking api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth

Start authorization for a user

POST

/sessions

Authorize the user session

GET

/accounts/{account_id}/balances

Get account balances

GET

/accounts/{account_id}/transactions

Get account transactions

POST

/payments

Initiate a payment

GET

/payments/{payment_id}

Get a payment by ID

GET

/aspsps

List supported ASPSPs

POST

/auth

Start authorization for a user

POST

/sessions

Authorize the user session

GET

/accounts/{account_id}/balances

Get account balances

GET

/accounts/{account_id}/transactions

Get account transactions

POST

/payments

Initiate a payment

Why Jentic?

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

Credential isolation

Enable Banking application tokens are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw application key never enters the agent's context, and Jentic injects the bearer at execution time.

Intent-based discovery

Agents search by intent (e.g., 'connect a European bank account') and Jentic returns matching Enable Banking operations with their input schemas, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Enable Banking integration: 2-4 days for session, consent, and payment initiation handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Enable Banking API through Jentic.

Why is there no official OpenAPI spec for Enable Banking API?

Enable Banking does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Enable Banking API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Enable Banking API use?

The API uses HTTP Bearer authentication. The application token is sent in the Authorization header on every request. Through Jentic the token is held encrypted in the vault and injected at execution time.

Can I initiate payments with the Enable Banking API?

Yes. POST /payments creates the payment, GET /payments/{payment_id} reports status, and DELETE /payments/{payment_id} cancels before settlement. Status polling is the recommended pattern.

How do I list supported European banks through Jentic?

Search Jentic for 'list European banks open banking', load the schema for GET /aspsps, and execute it. The response is the supported ASPSP catalogue, suitable for a bank-selection UI.

What are the rate limits for the Enable Banking API?

The OpenAPI spec does not declare quantitative rate limits. Enable Banking applies PSD2-aligned access limits per consented user; treat HTTP 429 responses as authoritative and back off accordingly.

Can I delete a session when a user revokes access?

Yes. DELETE /sessions/{session_id} ends the session so subsequent calls with that session ID fail. This is the correct path when a user revokes consent in your app.

Enable Banking API

Connect the Enable Banking API to your agent

Capabilities

Start building with Enable Banking API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs