canonical: https://jentic.com/apis/afterbanks.com/afterbanks-afterbanks-api

# Afterbanks API

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.

## For AI agents

Fetch real-time bank account data, transactions, and balances from Spanish and Latin American banks via the Afterbanks aggregator after end-user consent.

## Scope

Does not handle payment initiation, card processing, or accounting bookkeeping - use for read-only bank account aggregation only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'fetch afterbanks transactions', load the serviceV3 schema, and execute a daily refresh for a list of SMB customer references

## Key endpoints

| 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 |

## Key resources

- **User** — Authenticated Afterbanks user profile
- **forms** — Bank login forms used to drive the consent flow
- **serviceV3** — Core endpoint to fetch account and transaction data

## Why Jentic

- **Setup:** Wiring the Afterbanks API by hand means managing its API-key auth and coding calls against its bank-aggregation service endpoint. Through Jentic you install once, import the Afterbanks API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Afterbanks exposes a small read-only surface where account aggregation is driven through the request body of serviceV3, so limit the agent to the operations it needs, such as listing forms or reading account data. You choose which operations are in the allowed set, so anything you leave out is not reachable.
- **Credential handling:** Your Afterbanks partner API key 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.
- **Discovery method:** Agents search Jentic by intent such as '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 browsing the reference docs.

## Related APIs

- **Plaid API** — Open banking aggregator with deep US and EU coverage; alternative for projects outside Iberia or LatAm.
- **TrueLayer API** — European open banking platform with PSD2 coverage across the UK and EU.
- **Salt Edge API** — Global open banking aggregator with broad emerging-markets coverage.
- **Xero Accounting API** — Accounting platform that consumes bank feeds for reconciliation.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Afterbanks API?

Yes. Because you run Jentic One yourself, your own rules decide which Afterbanks operations and credentials the agent can use. The Afterbanks surface is small and read-only, so you can allow only the operations the agent needs, such as listing bank forms with GET /forms or reading account and transaction data with POST /serviceV3, and leave the rest out. Any operation you do not add to the allowed set is not reachable by the agent.