Db Deutsche Bank API

Name: Deutsche Bank API
Brand: Deutsche Bank API
Availability: InStock

✓ Official Vendor SpecFinanceBankingapiKey3 EndpointsREST

For Agents

Authenticate against the Deutsche Bank developer platform and enumerate or resolve bank-side resources via a small REST surface.

Install Jentic One Beta

Connect the Deutsche Bank API to your agent

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

Issue an authentication token via POST /auth/token

List bank-side resources via GET /resources

Resolve a single resource by ID via GET /resources/{id}

Drive token-aware flows for downstream Deutsche Bank developer products

GET STARTED

Start building with Deutsche Bank API

Explore with Jentic

View OpenAPI Document

The Deutsche Bank API is the open banking platform exposed by Deutsche Bank for partners and developers building on the bank's account, payment, and reference-data products. This spec covers the platform's core authentication primitive (POST /auth/token) plus a generic resources surface used to enumerate and resolve bank-side objects. Authentication is an API key in the X-API-Key header, with token issuance backing more sensitive operations. The wider Deutsche Bank developer programme expands these primitives into full PSD2 account information and payment initiation flows.

Use Cases

Patterns agents use Deutsche Bank API for, with concrete tasks.

★ Partner Authentication Bootstrap

Partners integrating with the Deutsche Bank developer platform start by exchanging their X-API-Key for a short-lived access token via POST /auth/token. That token then authorises subsequent calls into more sensitive Deutsche Bank products (account info, payment initiation) when the partner has the right entitlements. Bootstrapping the auth flow correctly is a prerequisite for any downstream banking integration.

Call POST /auth/token with the partner X-API-Key, store the returned token, and use it as the bearer for subsequent banking calls

Resource Discovery

Integrators use GET /resources to enumerate the resource records their partner credentials can see, then GET /resources/{id} to pull the canonical record. This is typically the first call in any onboarding flow, used to confirm scope and to seed downstream caches with the right reference identifiers.

Call GET /resources to list available reference records, then GET /resources/{id} for each to seed a local cache

Token Refresh for Long-running Jobs

Long-running data pipelines that call Deutsche Bank developer endpoints over many hours refresh their access token periodically by calling POST /auth/token again before the previous token expires. The pattern keeps batch jobs running through the night without manual credential rotation.

Schedule POST /auth/token every 50 minutes, replace the active token in memory, and resume the in-flight resource sync

AI Agent Banking Integration

AI agents that need to operate against the Deutsche Bank developer platform call the auth and resources endpoints through Jentic. Jentic isolates the X-API-Key in its vault and handles the token exchange, so the agent only deals with token references and resource IDs — never the raw partner secret.

Authenticate via POST /auth/token, list resources via GET /resources, and return a summary table of resource IDs for downstream payment flows

Key Endpoints

3 endpoints — the deutsche bank api is the open banking platform exposed by deutsche bank for partners and developers building on the bank's account, payment, and reference-data products.

METHOD

PATH

DESCRIPTION

POST

/auth/token

Issue an access token from a partner X-API-Key

GET

/resources

List accessible resource records

GET

/resources/{id}

Resolve a single resource record by ID

POST

/auth/token

Issue an access token from a partner X-API-Key

GET

/resources

List accessible resource records

GET

/resources/{id}

Resolve a single resource record by ID

Why Jentic?

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

Credential isolation

Deutsche Bank X-API-Key values are stored encrypted in the Jentic vault and the POST /auth/token exchange is handled by the platform. Agents receive scoped access tokens — neither the X-API-Key nor the raw partner credential ever enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'authenticate against Deutsche Bank' or 'list bank resources') and Jentic returns the matching operation with its input schema, so the agent calls POST /auth/token or GET /resources without browsing developer.db.com.

Time to first call

Direct Deutsche Bank developer integration: 1-3 days to wire X-API-Key auth, token exchange, and resource enumeration. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Deutsche Bank API through Jentic.

What authentication does the Deutsche Bank API use?

Deutsche Bank uses an API key passed in the X-API-Key header, exchanged for a short-lived access token via POST /auth/token. Through Jentic, the X-API-Key is stored encrypted in the MAXsystem vault and the token exchange is handled inside the platform.

Can I list resources with the Deutsche Bank API?

Yes. GET /resources lists the resource records your partner credentials can see, and GET /resources/{id} resolves a specific record. This is the typical entry point for onboarding flows.

What are the rate limits for the Deutsche Bank API?

Rate limits are governed by your partner agreement and are not declared in this OpenAPI spec; consult developer.db.com or your Deutsche Bank partner contact before running high-frequency token or resource calls.

How do I issue a Deutsche Bank access token through Jentic?

Search Jentic for 'issue a Deutsche Bank access token', load the POST /auth/token operation, and execute it. Jentic injects the X-API-Key automatically and returns the access token for use with downstream calls.

Does this spec cover account information and payment initiation?

This spec covers only authentication and resource discovery. Account information and payment initiation are part of separate Deutsche Bank developer products gated behind PSD2 entitlements and a stricter onboarding.

Is the Deutsche Bank developer programme open to any developer?

The sandbox is open to registered developers, but production access requires partnership onboarding through developer.db.com, including KYC and PSD2 compliance steps where applicable.