finAPI Access API

Name: finAPI Access API
Brand: finAPI Access API
Availability: InStock

✓ Official Vendor SpecFinanceBankingbearer, oauth215 EndpointsREST

For Agents

Provision end users and bank connections under a BaFin-licensed open banking platform via OAuth 2.0 and bearer tokens.

Install Jentic One Beta

Connect the finAPI Access API to your agent

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

Issue an OAuth 2.0 access token via POST /oauth/token using client credentials

Provision an end user under your finAPI client and link them to bank connections

Create a new bank connection by initiating the PSD2 SCA flow on POST /bankConnections

GET STARTED

Start building with finAPI Access API

Explore with Jentic

View OpenAPI Document

The finAPI Access API is a BaFin-licensed open banking interface that gives applications access to bank account data, payment initiation, and aggregated banking information across European institutions. It exposes 15 endpoints covering OAuth client-credentials token issuance, end-user provisioning, and bank-connection management. Authentication is by OAuth 2.0 client credentials for service-to-service calls and bearer tokens for end-user-scoped operations. The API is used by fintechs and embedded-finance products that need PSD2-compliant access to retail and SMB bank accounts in the DACH region and beyond.

Use Cases

Patterns agents use finAPI Access API for, with concrete tasks.

★ Embedded Open Banking Onboarding

Fintechs that need to read SMB transaction data can have an agent provision the end user via POST /users, then call POST /bankConnections to start the PSD2 strong customer authentication flow. Once consent is granted, the agent stores the connection id and downstream services can read account data through the same finAPI session.

Call POST /users to create the user, then POST /bankConnections with the bank id and SCA configuration, and store the connection id with the user record.

Consent Revocation Handling

Compliance teams operating under PSD2 need to honour consent revocations promptly. An agent can listen for revoke events from the host application and call DELETE /bankConnections/{id} on the finAPI side to ensure the bank connection is removed and no further data calls succeed against the revoked link.

On revoke event, look up the user's connection ids, then DELETE /bankConnections/{id} for each, then mark the host record as revoked.

Service-To-Service Token Refresh

Backend automations that hit finAPI on a schedule can have an agent refresh the OAuth client credentials token by calling POST /oauth/token before the previous token expires, then cache the new bearer for subsequent calls. This keeps the polling loop running without 401-driven retries.

On token expiry, call POST /oauth/token with the client credentials grant and replace the cached bearer used by the polling worker.

AI Agent finAPI Integration via Jentic

An agent connected to Jentic can search by intent (for example provision a finapi user) and Jentic returns the matching finAPI operation along with its input schema. The OAuth client credentials and per-user bearer tokens live in the Jentic vault, which is critical given finAPI's BaFin-licensed status. Integration drops from a multi-week PSD2 onboarding to under an hour.

Search Jentic for create a finapi bank connection, load POST /bankConnections, and execute with the user id and bank id while Jentic injects the bearer token from the vault.

Key Endpoints

15 endpoints — the finapi access api is a bafin-licensed open banking interface that gives applications access to bank account data, payment initiation, and aggregated banking information across european institutions.

METHOD

PATH

DESCRIPTION

POST

/oauth/token

Issue an OAuth access token

POST

/users

Provision a new end user

GET

/users

List end users under your client

DELETE

/users/{userId}

Delete an end user

GET

/bankConnections

List bank connections

POST

/bankConnections

Create a new bank connection

GET

/bankConnections/{id}

Retrieve a bank connection

DELETE

/bankConnections/{id}

Delete a bank connection

POST

/oauth/token

Issue an OAuth access token

POST

/users

Provision a new end user

GET

/users

List end users under your client

DELETE

/users/{userId}

Delete an end user

GET

/bankConnections

List bank connections

POST

Why Jentic?

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

Credential isolation

finAPI client credentials and per-user bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped references; the raw OAuth client secret never enters the agent's context, which matters for a BaFin-licensed integration.

Intent-based discovery

Agents search Jentic by intent (for example link a bank account) and Jentic returns the matching finAPI operation with its input schema, so the agent does not have to walk the full PSD2 spec.

Time to first call

Direct finAPI integration: 1-2 weeks across PSD2 onboarding, OAuth setup, and SCA handling. Through Jentic: under one hour to wire the agent calls - PSD2 commercial contract still required separately.

FAQs

Specific to using finAPI Access API through Jentic.

What authentication does the finAPI Access API use?

finAPI uses OAuth 2.0 client credentials for service tokens via POST /oauth/token, plus bearer tokens for per-user calls. Through Jentic, both the client credentials and user tokens live in the encrypted vault and are injected at execution.

Can I link a bank account with the finAPI Access API?

Yes. Provision the user via POST /users, then call POST /bankConnections to begin the PSD2 SCA flow against the chosen bank. Once the end user completes SCA, the connection becomes usable for downstream account information calls.

What are the rate limits for the finAPI Access API?

finAPI applies per-client throttling and the spec does not publish a fixed RPS. Sandbox traffic is limited more aggressively than production. Agents should respect 429 responses with exponential backoff and avoid bursting on /bankConnections during SCA flows.

How do I revoke a bank connection through Jentic?

Search Jentic for revoke a finapi bank connection, load the DELETE /bankConnections/{id} operation, and execute with the connection id. Jentic injects the bearer token from the vault and finAPI removes the connection on the bank side.

Is the finAPI Access API free to use?

finAPI offers a sandbox at sandbox.finapi.io for development, but production use against live.finapi.io requires a commercial agreement and a BaFin-licensed contract because the underlying service is regulated.

Can I list all bank connections for a user with finAPI?

Yes. Call GET /bankConnections with the user context to enumerate that user's links. Agents can then iterate the connections to refresh transaction data or surface revocation candidates.

finAPI Access API

Connect the finAPI Access API to your agent

Capabilities

Start building with finAPI Access API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs