Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the La Banque Postale PSD2 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%2Flabanquepostale.com%2Flabanquepostale" | shStep 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%2Flabanquepostale.com%2Flabanquepostale" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with La Banque Postale PSD2 API.
Retrieve a user's accounts and account owners via GET /v2/accounts and GET /v2/accounts/{id}/owners under AISP consent
Read account overdraft state and limits via GET /v2/accounts/{id}/overdrafts to inform spending decisions
List transaction history via GET /v2/transactions with date and account filters
Read account balances via GET /v2/balances for spending power and reconciliation
GET STARTED
Initiate payment requests via POST /v2/payment-requests under PISP consent
Confirm payment requests via POST /v2/payment-requests/{id}/confirmation after Strong Customer Authentication
Patterns agents use La Banque Postale PSD2 API for, with concrete tasks.
★ Account Aggregation (AISP)
Aggregate a customer's La Banque Postale balances and transactions into a personal-finance dashboard. Under PSD2 AISP consent, GET /v2/accounts enumerates the user's accounts, GET /v2/balances returns balances, and GET /v2/transactions returns paginated transaction history. Owners and overdrafts can be enriched on demand from /owners and /overdrafts.
GET /v2/accounts to list accounts, then GET /v2/balances and GET /v2/transactions for each account ID to populate a dashboard view.
Payment Initiation (PISP)
Initiate SEPA-style payments from a La Banque Postale account on behalf of an authorised user. POST /v2/payment-requests creates a payment request, the user authenticates with Strong Customer Authentication on the bank's side, and POST /v2/payment-requests/{id}/confirmation confirms execution. The intermediate state can be inspected via GET /v2/payment-requests/{id}.
POST /v2/payment-requests with debtor account, creditor account, and amount, await SCA, then POST /v2/payment-requests/{id}/confirmation to execute.
Reconciliation Pipeline
Pull La Banque Postale transactions into an accounting system for daily reconciliation. The agent reads /v2/transactions on a schedule, deduplicates against last-seen IDs, and writes new transactions into the ledger. /v2/balances acts as the daily closing-balance check.
GET /v2/transactions with the date range since the last sync, write new transactions into the ledger, and GET /v2/balances to record the day's closing balance.
AI Agent Banking Assistant
An assistant in a banking app reads balances, summarises spending, and initiates payments on instruction from the account owner. Through Jentic, the assistant calls La Banque Postale's PSD2 endpoints by intent without holding the OAuth refresh token in the agent context, and SCA stays inside the bank's own flow.
On 'pay 250 EUR to my landlord today', POST /v2/payment-requests with the saved beneficiary IBAN and 250 EUR, then prompt for SCA and POST /v2/payment-requests/{id}/confirmation.
8 endpoints — jentic publishes the only available openapi specification for la banque postale psd2 api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v2/accounts
Retrieve accessible accounts (AISP)
/v2/balances
Retrieve balances
/v2/transactions
Retrieve transactions
/v2/payment-requests
Initiate a payment request (PISP)
/v2/payment-requests/{id}/confirmation
Confirm a payment request after SCA
/v2/accounts/{id}/owners
Retrieve account owners
/v2/accounts/{id}/overdrafts
Retrieve account overdrafts
/v2/accounts
Retrieve accessible accounts (AISP)
/v2/balances
Retrieve balances
/v2/transactions
Retrieve transactions
/v2/payment-requests
Initiate a payment request (PISP)
/v2/payment-requests/{id}/confirmation
Confirm a payment request after SCA
/v2/accounts/{id}/owners
Retrieve account owners
/v2/accounts/{id}/overdrafts
Retrieve account overdrafts
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the La Banque Postale PSD2 API by hand means running the OAuth2 authorization-code flow, tracking the aisp and pisp scopes, and rotating tokens against api.labanquepostale.com yourself. Through Jentic you install once, import the La Banque Postale PSD2 API from the API Directory, store the OAuth credentials once, and your agent calls it.
Permission scoping
La Banque Postale gates access by PSD2 OAuth scope, so scope the agent to the operations it needs, such as reading accounts, balances, and transactions under the aisp scope. You choose that set, so payment-initiation operations under pisp are not included unless you add them.
Credential isolation
Your La Banque Postale OAuth tokens are stored once, encrypted, by your own Jentic One instance, which rotates them at execution time. The long-lived banking credentials never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read La Banque Postale balances' or 'initiate a SEPA payment', and Jentic returns the matching PSD2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using La Banque Postale PSD2 API through Jentic.
Why is there no official OpenAPI spec for La Banque Postale PSD2 API?
La Banque Postale publishes documentation on developer.labanquepostale.com but does not expose a single canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call La Banque Postale PSD2 API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the La Banque Postale PSD2 API use?
The API uses OAuth 2.0 authorization code flow under PSD2 rules. The user authenticates with the bank, grants AISP or PISP scopes to a licensed third-party provider, and the access token is then included on each request. Through Jentic, tokens are stored encrypted in your Jentic One instance.
Can I initiate a payment with the La Banque Postale PSD2 API?
Yes. POST /v2/payment-requests creates the payment request, and POST /v2/payment-requests/{id}/confirmation finalises it after the user completes Strong Customer Authentication. GET /v2/payment-requests/{id} reads the current status.
How do I read account balances through Jentic?
Search Jentic for 'retrieve La Banque Postale balances'. Jentic returns GET /v2/balances with its schema. Provide the account context resolved from /v2/accounts and Jentic executes the call using the stored OAuth access token.
Do I need a PSD2 licence to use the La Banque Postale PSD2 API?
Yes. AISP endpoints require an AISP licence and PISP endpoints require a PISP licence (or registered agent status). The bank validates the third-party provider's eIDAS QWAC certificate during the OAuth flow.
What rate limits apply to the La Banque Postale PSD2 API?
PSD2 introduces minimum service-quality requirements rather than fixed rate limits. Refer to developer.labanquepostale.com for the current operational limits and aggregator-specific ceilings before scaling agent traffic.
Can I limit what my agent is allowed to do with the La Banque Postale PSD2 API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. La Banque Postale gates access by PSD2 OAuth scope, so you can grant only the AISP read operations such as GET /v2/accounts, GET /v2/balances, and GET /v2/transactions and leave out the PISP payment operations. If you never add POST /v2/payment-requests or POST /v2/payment-requests/{id}/confirmation, the agent cannot initiate or confirm a payment.
Know of an official OpenAPI document? Contribute it →
For Agents
Access La Banque Postale PSD2 open banking endpoints: read account balances, owners, overdrafts, and transactions, and initiate or confirm payment requests.
Use for: I need to read the customer's La Banque Postale account balances, I want to initiate a SEPA payment from a La Banque Postale account, List recent transactions on a La Banque Postale account, Retrieve the owners of a given account
Not supported: Does not handle card issuing, lending decisions, or non-PSD2 corporate banking - use for La Banque Postale AISP and PISP open banking only.
Jentic publishes the only available OpenAPI specification for La Banque Postale PSD2 API, keeping it validated and agent-ready. La Banque Postale's PSD2 API exposes regulated open banking endpoints for licensed third-party providers: Account Information Service Provider (AISP) endpoints for account balances, owners, overdrafts, and transactions, and Payment Initiation Service Provider (PISP) endpoints for initiating, retrieving, and confirming payment requests. Authentication uses OAuth 2.0 authorization code flow with PSD2-style scopes.