BANKS/Connect API Reference

Name: BANKS/Connect API Reference API
Brand: BANKS/Connect API Reference
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbasic, bearer57 EndpointsREST

For Agents

Administer BANKSapi tenants, mint OAuth2 tokens, and orchestrate end-to-end PSD2 bank access, consent, and payment flows for European banking customers. Used by agents managing the full lifecycle of an open banking integration.

Quickstart

Get started with BANKS/Connect API Reference in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"mint a banksapi oauth2 token"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BANKS/Connect API Reference API.

Manage tenants and tenant-scoped users through Auth management endpoints

Mint, introspect, and revoke OAuth2 tokens for service authentication

Provision customer bank accesses and orchestrate consent grant flows

Initiate customer payments and SEPA Ueberweisungen on consented accounts

GET STARTED

Start building with BANKS/Connect API Reference API

Explore with Jentic

View OpenAPI Document

Use for: Provision a new tenant user under our BANKSapi account, Mint an OAuth2 token for server-to-server access, Revoke an OAuth2 token that has been compromised, Initiate a customer payment through a consented bank access

Not supported: Does not handle card issuing, KYC document verification, or general accounting ledgers — use for BANKSapi tenant administration, OAuth2 token management, and PSD2 customer banking workflows only.

Jentic publishes the only available OpenAPI document for BANKS/Connect API Reference, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the BANKS/Connect API Reference, keeping it validated and agent-ready. BANKS/Connect v2 is the full-surface BANKSapi platform covering tenant and user administration, OAuth2 token management, customer bank access, payment initiation, REG/Protect compliance flows, and provider metadata. Operators administer tenants and users through the Auth management endpoints, mint and revoke OAuth2 tokens, and orchestrate end-customer banking through the Customer Bank Access, Customer Consent, and Customer Payment surfaces. This is the deeper administrative surface complementing the higher-level BANKS/Connect summary endpoints.

Use Cases

Patterns agents use BANKS/Connect API Reference API for, with concrete tasks.

★ Multi-Tenant Open Banking Platform Operations

Run a multi-tenant open banking platform where each tenant has its own users, OAuth2 tokens, and customer base. The BANKS/Connect v2 Auth management surface handles tenant-scoped user lifecycle including create, deactivate, reactivate, and update operations, while the OAuth2 endpoints manage the token lifecycle. Suitable for fintech operators serving multiple banks or merchants under one BANKSapi contract.

Create a tenant user via POST /auth/mgmt/v1/tenants/{tenant-name}/users, then mint an OAuth2 access token via POST /auth/oauth2/token for that user.

End-to-End Customer Payment Flow

Drive a complete customer payment journey from bank access creation through consent grant to SEPA Ueberweisung initiation. The Customer Bank Access, Customer Consent, and Customer Ueberweisung surfaces work together to guide the end user through PSD2-compliant authorisation and trigger the actual transfer once consent is in place. Useful for invoicing, payroll-style payouts, and account-funded checkout.

Create a customer bank access, wait for consent grant, then call the Customer Ueberweisung endpoint to initiate a 500 EUR SEPA transfer and confirm completion.

Compliance and Provider Health Monitoring

Monitor the health of provider connections and run regulated compliance checks (REG/Protect) for workflows that need additional verification. Provider job statistics surface success and error counts across the connected bank network so operators can detect outages early. Pair with the Encrypt endpoint to wrap sensitive payloads when integrating with downstream regulated systems.

Pull provider job statistics via GET /providers/v2/statistics/jobs and alert if error rate for a specific provider exceeds 5% in the last hour.

AI Agent Banking Operations Assistant via Jentic

Run an internal operations assistant that can provision new tenant users, rotate OAuth2 tokens, and inspect customer consent state on demand. The agent searches Jentic for an intent like 'create a tenant user' or 'revoke an oauth2 token', loads the matched operation schema, and executes the call with credentials held in the Jentic vault. This avoids exposing tenant admin credentials to the LLM context.

Search Jentic for 'revoke an oauth2 token', execute POST /auth/oauth2/revoke with the compromised token id, and confirm revocation status.

Key Endpoints

57 endpoints — jentic publishes the only available openapi specification for the banks/connect api reference, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/mgmt/v1/tenants/{tenant-name}/users

Create a tenant user

POST

/auth/oauth2/token

Mint an OAuth2 access token

POST

/auth/oauth2/revoke

Revoke an OAuth2 token

GET

/auth/oauth2/introspect

Introspect an OAuth2 token

GET

/providers/v2

List supported bank providers

GET

/providers/v2/statistics/jobs

Get provider job run statistics

PUT

/encrypt

Encrypt plaintexts for secure transmission

POST

/auth/mgmt/v1/tenants/{tenant-name}/users

Create a tenant user

POST

/auth/oauth2/token

Mint an OAuth2 access token

POST

/auth/oauth2/revoke

Revoke an OAuth2 token

GET

/auth/oauth2/introspect

Introspect an OAuth2 token

GET

/providers/v2

List supported bank providers

Why though Jentic?

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

Credential isolation

BANKSapi basic credentials and OAuth2 bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access, and tokens are injected at request time so the LLM context never holds raw secrets.

Intent-based discovery

Agents search Jentic by intent (for example, 'mint an oauth2 token' or 'list bank providers') and Jentic returns the matching BANKS/Connect operations with their input schemas, including the right authentication scheme.

Time to first call

Direct BANKSapi v2 integration: 2-3 weeks for tenant setup, OAuth2 wiring, and consent orchestration. Through Jentic: under 2 hours once tenant credentials are stored, since search-load-execute replaces handcrafted clients.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BANKSapi BANKS/Connect API

The high-level BANKS/Connect surface focused on bank access, transactions, and payments.

Use banksapi.de/main for the day-to-day customer banking flows; use banksapi.io/main when you need full tenant administration and OAuth2 token management.

Alternative

Plaid

North American and UK bank account aggregation platform.

Plaid suits US, Canadian, and UK coverage; BANKS/Connect is stronger for DACH-region PSD2 use cases with deeper tenant administration.

Alternative

TrueLayer

European open banking platform with strong UK payment initiation.

Choose TrueLayer for UK-led open banking payments; choose BANKS/Connect for DACH coverage and full tenant administration.

FAQs

Specific to using BANKS/Connect API Reference API through Jentic.

Why is there no official OpenAPI spec for BANKS/Connect API Reference?

BANKSapi does not publish an OpenAPI specification for its full v2 surface. Jentic generates and maintains this spec so that AI agents and developers can call BANKS/Connect 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 BANKS/Connect API Reference use?

The API supports both HTTP basic authentication and HTTP bearer tokens. OAuth2 access tokens are minted via POST /auth/oauth2/token and presented as bearer credentials on protected calls. When called through Jentic, both basic credentials and bearer tokens are isolated in the encrypted vault.

How do I mint an OAuth2 token in BANKS/Connect?

Call POST /auth/oauth2/token with grant type and client credentials. The response includes an access_token and expiry; cache and refresh before expiry. To invalidate a leaked token call POST /auth/oauth2/revoke with the token value.

Can I initiate SEPA payments with BANKS/Connect v2?

Yes. The Customer Ueberweisung and Customer Bank Access Payment surfaces let you initiate SEPA credit transfers from a consented customer bank access. Consent must be active before initiation; check status via the Customer Consent endpoints before submitting the transfer.

What are the rate limits for the BANKSapi BANKS/Connect API?

Rate limits are tenant-scoped and defined in your contract rather than published globally. For provider polling, use the /providers/v2/statistics/jobs endpoint to monitor health and avoid retry storms when a single provider is degraded.

How do I provision a new tenant user through Jentic?

Install the Jentic SDK with pip install jentic, search for 'create a tenant user', and execute POST /auth/mgmt/v1/tenants/{tenant-name}/users with the user details. Jentic injects the management credentials at execution time so the agent never sees the admin secret.