Postbank Bulgaria Open Banking API

Name: Postbank Bulgaria Open Banking API API
Brand: Postbank Bulgaria Open Banking API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth210 EndpointsREST

For Agents

Access Postbank Bulgaria accounts, initiate SEPA and domestic transfers, and confirm fund availability under PSD2 open banking consent.

Connect the Postbank Bulgaria Open Banking API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Postbank Bulgaria Open Banking API API.

Retrieve customer account lists and individual account details with IBAN and currency

Query account balances and transaction histories with date-range filtering

Initiate domestic budget transfers and SEPA credit transfers with debtor and creditor IBANs

Manage AIS consent lifecycle including creation, status checks, and revocation

GET STARTED

Start building with Postbank Bulgaria Open Banking API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Postbank Bulgaria Open Banking API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Postbank Bulgaria Open Banking API, keeping it validated and agent-ready. Postbank Bulgaria Open Banking API implements the PSD2 directive with Account Information Services (AIS), Payment Initiation Services (PIS), and Confirmation of Funds Services (CFS). It enables third-party providers to access customer account data with consent, initiate domestic budget transfers and SEPA credit transfers, and confirm fund availability for payment requests. The API uses OAuth 2.0 authorization code flow with scopes for each service.

Use Cases

Patterns agents use Postbank Bulgaria Open Banking API API for, with concrete tasks.

★ Account Aggregation for Fintech Apps

Retrieve account lists, balances, and transaction histories from Postbank Bulgaria customer accounts under PSD2 consent. The API supports date-range filtering on transactions and returns both booked and pending entries, enabling fintech applications to present unified financial views across multiple banks.

Create an AIS consent via /v1/consents, then list accounts using /v1/accounts and retrieve balances for the first account

Payment Initiation for Business Transfers

Initiate domestic budget transfers or SEPA credit transfers on behalf of customers who have authorized the payment via the PSD2 consent flow. The API accepts debtor and creditor IBANs with an instructed amount and currency, returning a payment ID and transaction status for tracking.

Initiate a SEPA credit transfer for 100.00 EUR from debtor IBAN BG1234 to creditor IBAN DE5678 using the /v1/payments/sepa-credit-transfers endpoint

Pre-Payment Funds Verification

Confirm whether a customer account has sufficient funds for a specific transaction amount before initiating payment. The Confirmation of Funds endpoint returns a boolean fundsAvailable response, enabling merchants and payment processors to verify solvency without accessing full account details.

Call /v1/funds-confirmations with account IBAN BG1234 and instructed amount of 500.00 BGN to verify fund availability

AI Agent Banking Integration via Jentic

AI agents use Jentic to discover Postbank open banking operations by intent, such as 'check account balance' or 'initiate a bank transfer'. Jentic returns the operation schema with OAuth 2.0 scope requirements and input parameters, handling token acquisition so agents access banking data without managing PSD2 consent flows directly.

Search Jentic for 'check bank account balance', load the getAccountBalances schema, and execute with account-id to retrieve current balance data

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for postbank bulgaria open banking api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/accounts

List all accessible customer accounts

GET

/v1/accounts/{account-id}

Get details for a specific account

GET

/v1/accounts/{account-id}/balances

Retrieve account balances

GET

/v1/accounts/{account-id}/transactions

Get account transactions with date filtering

POST

/v1/consents

Create an AIS consent for account access

POST

/v1/payments/{payment-product}

Initiate a domestic or SEPA transfer

GET

/v1/payments/{payment-product}/{paymentId}

Get payment status

POST

/v1/funds-confirmations

Confirm fund availability for an amount

GET

/v1/accounts

List all accessible customer accounts

GET

/v1/accounts/{account-id}

Get details for a specific account

GET

/v1/accounts/{account-id}/balances

Retrieve account balances

GET

/v1/accounts/{account-id}/transactions

Get account transactions with date filtering

POST

/v1/consents

Create an AIS consent for account access

Why though Jentic?

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

Credential isolation

Postbank OAuth 2.0 client credentials and access tokens are stored encrypted in the Jentic vault. Agents receive scoped tokens with the appropriate PSD2 scope (ais, pis, or cfs) without managing the authorization code flow directly.

Intent-based discovery

Agents search by intent (e.g., 'check bank account balance' or 'initiate a SEPA transfer') and Jentic returns the matching Postbank operation with its required parameters and OAuth scope, so the agent calls the right endpoint without navigating PSD2 consent flows.

Time to first call

Direct Postbank integration: 3-5 days for OAuth setup, consent management, and PSD2 compliance handling. Through Jentic: under 1 hour — search, load schema, execute with managed authentication.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Nordigen API

PSD2 aggregator providing access to 2000+ European banks through a single API

Choose Nordigen when you need to access multiple European banks through a single integration rather than connecting directly to Postbank Bulgaria alone.

Alternative

TrueLayer API

Open banking platform with account data and payment initiation across EU and UK banks

Choose TrueLayer when you need multi-bank connectivity across the EU and UK with a unified data model, not just Postbank Bulgaria.

Complementary

Plaid API

Financial data aggregation covering US and international banks

Use Plaid alongside Postbank when you need account data from non-EU banks or require additional financial data enrichment like category classification.

FAQs

Specific to using Postbank Bulgaria Open Banking API API through Jentic.

Why is there no official OpenAPI spec for Postbank Bulgaria Open Banking API?

Postbank Bulgaria does not publish an OpenAPI specification for its PSD2 APIs. Jentic generates and maintains this spec so that AI agents and developers can call Postbank Bulgaria Open 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 Postbank Bulgaria Open Banking API use?

The API uses OAuth 2.0 authorization code flow with three scopes: ais (Account Information), pis (Payment Initiation), and cfs (Confirmation of Funds). Authorization is at https://api.postbank.bg/oauth/authorize and tokens are obtained from https://api.postbank.bg/oauth/token. Through Jentic, OAuth tokens are managed automatically.

Can I initiate SEPA transfers through the Postbank Bulgaria API?

Yes. The /v1/payments/sepa-credit-transfers endpoint accepts a payment request with debtor account IBAN, creditor account IBAN, and an instructed amount with currency. The API returns a payment ID and transaction status. The API also supports domestic-budget-transfers as a payment product.

What are the rate limits for the Postbank Bulgaria Open Banking API?

PSD2 regulations require banks to provide reasonable access. Specific rate limits are not published in the specification. Postbank follows standard NextGenPSD2 guidelines which typically allow 4 access requests per day for account information without active customer involvement.

How do I retrieve account transactions through the Postbank API with Jentic?

Install the SDK with pip install jentic, then search for 'retrieve bank account transactions'. Jentic returns the getAccountTransactions operation schema requiring an account-id path parameter and optional dateFrom and dateTo query parameters. Execute the call to receive booked and pending transaction records.

What consent management is required for account access?

Before accessing account data, you must create an AIS consent via POST /v1/consents. The consent has a validUntil date and a status (received, valid, rejected, expired). You can check consent status with GET /v1/consents/{consentId} and revoke it with DELETE /v1/consents/{consentId}. All account endpoints require an active consent.