Afterbanks API
Browse all Afterbanks APIs★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey3 EndpointsREST
For Agents
Fetch real-time bank account data, transactions, and balances from Spanish and Latin American banks via the Afterbanks aggregator after end-user consent.
Use for: I need to fetch a customer's bank transactions through Afterbanks, List the supported bank login forms for Spain, Get the current account balance for an Afterbanks-connected user, Retrieve the profile of the authenticated Afterbanks user
Not supported: Does not handle payment initiation, card processing, or accounting bookkeeping — use for read-only bank account aggregation only.
Jentic publishes the only available OpenAPI specification for Afterbanks API, keeping it validated and agent-ready. Afterbanks is a Spanish open-banking aggregator that standardises real-time access to bank account data across Spanish, Portuguese, and Latin American banks. The API exposes a small surface — bank form discovery, user account info, and the V3 bank-data service — that lets fintech and lending apps fetch transactions and balances from end-customer bank accounts after consent.
Install Jentic One Beta
Connect the Afterbanks API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Afterbanks 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with Afterbanks API.
List the bank login forms available for a country to drive an end-user consent flow
Retrieve the authenticated Afterbanks user profile via the /me endpoint
Pull aggregated account, balance, and transaction data for a connected bank user via serviceV3
Refresh bank data on demand for a previously connected end customer
Identify which Afterbanks-supported bank a customer connected with
Use Cases
Patterns agents use Afterbanks API for, with concrete tasks.
★ Lending Underwriting in Iberia and LatAm
Spanish and Latin American lenders use Afterbanks to pull a borrower's last 90-365 days of bank transactions during the loan application flow. The serviceV3 endpoint returns categorised transactions and balances after the borrower completes the bank login, letting underwriting models run cash-flow analysis without paper statements. Typical decisioning latency drops from days to minutes.
Call POST /serviceV3 with a connected user's credentials reference and return the last 90 days of transactions plus the current balance
Personal Finance Aggregation
PFM and budgeting apps use Afterbanks to pull a user's accounts and transactions across multiple Spanish and LatAm banks into a single dashboard. /forms drives the bank picker UI, and /serviceV3 refreshes balances on a scheduled job. Coverage spans the major retail banks in Spain, Portugal, Mexico, and several other Latin American markets.
List forms via GET /forms for country code 'ES', present the bank picker, then refresh transactions via POST /serviceV3 after the user authenticates
Accounting Reconciliation
Accounting and ERP integrations use Afterbanks to import bank transactions for SMB customers and reconcile them against booked invoices. The serviceV3 response is parsed into a ledger feed that the accounting tool matches to existing entries. This avoids the manual CSV upload most Spanish SMBs still rely on.
Pull the last 30 days of transactions via /serviceV3 for an SMB customer's primary account and emit a CSV ready for the accounting tool
AI Agent Cash-Flow Monitoring
Through Jentic, an agent can monitor an SMB's bank cash flow by polling Afterbanks on a schedule and flagging anomalies — large outflows, negative balance risk, repeated failed direct debits. The agent calls /serviceV3 through Jentic without storing the Afterbanks API key, and Jentic enforces credential isolation per call.
Search Jentic for 'fetch afterbanks transactions', load the serviceV3 schema, and execute a daily refresh for a list of SMB customer references
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for afterbanks api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/forms
List bank login forms for the consent flow
GET
/me
Retrieve the authenticated user profile
POST
/serviceV3
Fetch account and transaction data for a connected bank user
GET
/forms
List bank login forms for the consent flow
GET
/me
Retrieve the authenticated user profile
POST
/serviceV3
Fetch account and transaction data for a connected bank user
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Afterbanks partner API keys are stored encrypted in the Jentic vault. Agents receive scoped access at execution time and never hold the raw key, which is critical given the regulated banking data exposure.
Intent-based discovery
Agents search Jentic by intent (e.g., 'fetch bank transactions for a customer') and Jentic returns the matching Afterbanks operation with its parameter schema, so the agent calls the right endpoint without reading Afterbanks docs.
Time to first call
Direct Afterbanks integration: 3-5 days including consent flow handling and error recovery. Through Jentic: under 1 hour — search, load schema, execute against a connected user reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Afterbanks API through Jentic.
Why is there no official OpenAPI spec for Afterbanks API?
Afterbanks does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Afterbanks 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 Afterbanks API use?
Afterbanks uses an API key issued by Afterbanks for partner integrations. Through Jentic, the key is stored encrypted in the credential vault and only injected at execution time, so the agent never sees the raw secret.
Can I fetch a customer's transactions with the Afterbanks API?
Yes. After the customer authenticates against their bank via the /forms-driven flow, call POST /serviceV3 with the user reference to receive the account list, balances, and transaction history in a single response.
What are the rate limits for the Afterbanks API?
The public spec does not document fixed rate limits. Practically, Afterbanks throttles based on the partner contract — keep refreshes for active users to a few times per day and back off on HTTP 429.
How do I refresh bank data through Jentic?
Search Jentic for 'fetch afterbanks transactions', load the schema for POST /serviceV3, and execute it with the user reference for the connected customer. Jentic returns the parsed transaction list to the agent without exposing the Afterbanks key.
Which countries and banks does Afterbanks cover?
Afterbanks focuses on Spain and Portugal plus several Latin American markets including Mexico. Use GET /forms with a country code to discover the supported banks and the field shape needed for the consent flow.
GET STARTED