Install Jentic One Beta

Connect the BANKSapi BANKS/Connect API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BANKSapi BANKS/Connect 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbanksapi.de%2Fbanksapi-de" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbanksapi.de%2Fbanksapi-de" | 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 BANKSapi BANKS/Connect API.

Provision and manage end users and customer records under a tenant

Create bank accesses to link customer bank accounts under PSD2 consent

Retrieve transaction history for a linked bank access

Initiate SEPA credit transfer payments and check their status

Manage PSD2 consent lifecycle including status checks and cancellation

GET STARTED

Start building with BANKSapi BANKS/Connect API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Account Aggregation for Personal Finance Apps

Build a personal finance manager that connects German and DACH-region bank accounts under PSD2 and aggregates transactions for budgeting and categorisation. BANKS/Connect handles the consent flow, provider redirects, and transaction retrieval, so the app focuses on UX and analytics rather than maintaining bank-specific scrapers. A typical aggregation flow takes a few days to integrate end to end.

Create a bank access via POST /bankaccesses for customer C-123, then call GET /bankaccesses/{bankAccessId}/transactions to pull the last 90 days of transactions.

Lending Pre-Qualification with Bank Data

Pull a borrower's recent transaction history under PSD2 consent to inform underwriting and pre-qualification decisions for consumer or SME lending. BANKS/Connect provides categorisation-ready transaction data and consent management, so risk teams can build affordability checks without negotiating direct bank integrations. Consent-based access keeps the workflow GDPR and PSD2 compliant.

Initiate a bank access for the loan applicant, retrieve 6 months of transactions via /bankaccesses/{bankAccessId}/transactions, and calculate average monthly inflow.

Payment Initiation for SaaS Billing

Trigger SEPA credit transfers directly from a customer's bank account for B2B invoicing or payroll-style payouts, avoiding card fees and direct debit chargeback risk. BANKS/Connect's payment initiation flow uses PSD2 consent to authorise each transfer, with status tracking via the consent endpoints. Useful for SaaS billing, marketplaces, and treasury automation in the eurozone.

Call POST /payments to initiate a 250 EUR SEPA credit transfer from a customer bank access and poll /consent/{consentId} until status is authorised.

AI Agent Open Banking Assistant via Jentic

Run an AI assistant that helps small business owners review cashflow by summarising last week's transactions across linked bank accounts. The agent searches Jentic for 'get bank transactions for a customer', loads the BANKS/Connect schema, and executes the call with the customer's consented bank access ID. Jentic isolates the bearer token so it never enters the agent context.

Search Jentic for 'list transactions for a bank access', execute against bankAccessId 'BA-789', and summarise the top 5 outflows from the last 7 days.

Key Endpoints

13 endpoints — jentic maintains a curated, agent-ready openapi specification covering 13 banks/connect operations; banksapi publishes its own official openapi document for the full api surface.

METHOD

PATH

DESCRIPTION

POST

/bankaccesses

Create a bank access link under PSD2 consent

GET

/bankaccesses/{bankAccessId}/transactions

Retrieve transactions for a linked bank access

POST

/payments

Initiate a SEPA payment

GET

/consent/{consentId}

Check the status of a PSD2 consent

DELETE

/consent/{consentId}

Cancel an active PSD2 consent

GET

/providers

List supported bank providers

POST

/users

Create a tenant user

POST

/bankaccesses

Create a bank access link under PSD2 consent

GET

/bankaccesses/{bankAccessId}/transactions

Retrieve transactions for a linked bank access

POST

/payments

Initiate a SEPA payment

GET

/consent/{consentId}

Check the status of a PSD2 consent

DELETE

/consent/{consentId}

Cancel an active PSD2 consent

GET

/providers

List supported bank providers

POST

/users

Create a tenant user

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BANKSapi BANKS/Connect API by hand means managing tenant bearer tokens, tracking PSD2 consent lifecycles, and threading bank access ids through the aggregation and payment calls yourself. Through Jentic you install once, import the BANKS/Connect API from the API Directory, store the tenant token once, and your agent calls it.

Permission scoping

BANKS/Connect puts the bank access id and consent id in the URL path (/bankaccesses/{bankAccessId}/transactions and /consent/{consentId}), so a rule can pin your agent to one bank access: it reads that account's transactions and nothing else. You choose the operations it may call, so destructive ones like consent deletion or SEPA payment initiation are not included unless you add them.

Credential isolation

Your BANKSapi tenant bearer token 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.

Intent-based discovery

Agents search Jentic by intent such as 'get transactions for a bank account' or 'initiate a SEPA payment', and Jentic returns the matching BANKS/Connect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BANKSapi BANKS/Connect API through Jentic.

Does BANKSapi publish an official OpenAPI specification?

Yes. BANKSapi publishes an official OpenAPI 3.0 document titled 'BANKSapi API Reference' (version 2.0), embedded in its reference page at https://docs.banksapi.de/api/banks-connect.html and covering 47 path templates for BANKS/Connect. The specification Jentic serves on this page is a curated 13-operation subset focused on account access, transactions, and SEPA payments, validated against the live API; adopting the vendor's full document is tracked in Jentic's spec ledger. Get started with Jentic One, the self-hosted execution layer.

What authentication does the BANKSapi BANKS/Connect API use?

The API uses HTTP bearer token authentication. Each request must include an Authorization header carrying a tenant-scoped bearer token. When called through Jentic, the token is held in the encrypted vault and never exposed to the agent's context, while requests are signed at execution time.

Can I retrieve bank transactions with BANKS/Connect?

Yes. After creating a bank access via POST /bankaccesses under valid PSD2 consent, you can call GET /bankaccesses/{bankAccessId}/transactions to retrieve transaction history for the linked account. The depth of history depends on what each provider exposes under PSD2.

How do I initiate a payment with the BANKSapi API?

Call POST /payments with the source bank access, target IBAN, amount, and reference. The API returns a consent reference; poll GET /consent/{consentId} until the status indicates the customer has authorised the payment with their bank, then the SEPA transfer proceeds.

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

Rate limits are defined per tenant contract rather than published globally. For high-volume transaction polling, prefer scheduled aggregation windows over continuous polling and cache provider metadata fetched via /providers locally to stay within tenant quotas.

How do I link a bank account through Jentic?

Install the Jentic SDK with pip install jentic, search for 'link a bank account under psd2', and execute the matched POST /bankaccesses operation with the customer ID and provider. Jentic injects the bearer token at execution and returns the consent URL the end user must visit to authorise the link.

Can I limit what my agent is allowed to do with the BANKSapi BANKS/Connect API?

Yes. Jentic One runs self-hosted, so your own rules decide which BANKS/Connect operations and credentials the agent may use. Because the bank access id and consent id sit in the URL path (GET /bankaccesses/{bankAccessId}/transactions and /consent/{consentId}), you can pin the agent to a single bank access so it reads only that account's transactions and nothing else. You choose the operations it may call, so destructive ones such as consent cancellation (DELETE /consent/{consentId}) or SEPA payment initiation (POST /payments) stay out of reach unless you add them.

Banksapi De BANKSapi BANKS/Connect API

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

Agent-ready OpenAPI document · curated by JenticFinanceBankingbearer13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Connect to European bank accounts under PSD2, pull transactions, and initiate payments through the BANKSapi BANKS/Connect aggregation layer. Suitable for agents building open banking workflows in the DACH region.

Use for: Link a German bank account to my application under PSD2, Retrieve the last 90 days of transactions for a connected bank access, Initiate a SEPA credit transfer from a customer's account, Check the consent status for a bank account link

Not supported: Does not handle card issuing, KYC document verification, or accounting ledger storage - use for PSD2 bank account aggregation, transaction retrieval, and SEPA payment initiation only.

Jentic maintains a curated, agent-ready OpenAPI specification covering 13 BANKS/Connect operations; BANKSapi publishes its own official OpenAPI document for the full API surface. BANKS/Connect is BANKSapi's PSD2-compliant banking aggregation API that exposes account access, transaction retrieval, payment initiation, and consent management across European banks. Tenant administrators provision users and customers, link bank accesses, fetch transaction histories, and trigger SEPA credit transfers under explicit PSD2 consent flows. The API is targeted at fintech operators in the DACH region building budgeting, lending, or open banking products.

Jentic One on Github View OpenAPI Document

Connect the BANKSapi BANKS/Connect API to your agent

Capabilities

Start building with BANKSapi BANKS/Connect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Banksapi De BANKSapi BANKS/Connect API