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

# Afterbanks API Extendida

La estandarización de la conexión con cualquier banco en tiempo real. The API exposes 30 endpoints.

## For AI agents

Programmatically ficheros norma 43 disponibles desde el día actual hasta una fecha dada., lista de bancos soportados en files. Covers 30 operations.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Ficheros norma 43 disponibles desde el día actual hasta una fecha dada.
- Lista de bancos soportados en Files
- Método para obtener la identificación de titular.
- Query and filter Afterbanks API Extendida records by parameters
- Monitor Afterbanks API Extendida operational status and events

## Use cases

### Finance and Accounting Operations

Use the Afterbanks API Extendida to perform finance operations programmatically. The API provides 30 endpoints covering core functionality including ficheros norma 43 disponibles desde el día actual hasta una fecha dada., lista de bancos soportados en files, ficheros norma 19 (devoluciones) disponibles desde el día actual hasta una fecha.

Example prompt: Call POST /Files to ficheros norma 43 disponibles desde el día actual hasta una fecha dada.

### Automated Batch Management

Automate batch operations by combining multiple Afterbanks API Extendida endpoints. Agents can lista de bancos soportados en files and then ficheros norma 19 (devoluciones) disponibles desde el día actual hasta una fecha in a single workflow.

Example prompt: Call GET /Files/forms to lista de bancos soportados en files, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Afterbanks API Extendida endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'ficheros norma 43 disponibles desde el día actual hasta una fecha dada.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /Files | Ficheros norma 43 disponibles desde el día actual hasta una fecha dada. |
| GET | /Files/forms | Lista de bancos soportados en Files |
| POST | /Files19 | Ficheros norma 19 (devoluciones) disponibles desde el día actual hasta una fecha |
| GET | /Files19/forms | Lista de bancos soportados en Files19 |
| POST | /Files57 | Ficheros de recaudaciones disponibles en un rango de fechas dadas. |
| GET | /Files57/forms | Lista de bancos soportados en Files57 |
| POST | /ID | Método para obtener la identificación de titular. |
| GET | /ID/forms | Lista de bancos soportados en ID |

## Key resources

- **Batch** — Operations related to Batch
- **Categorization** — Operations related to Categorization
- **DirectDebits** — Operations related to DirectDebits
- **Files** — Operations related to Files
- **ID** — Operations related to ID

## Why Jentic

- **Setup:** Wiring the Afterbanks API Extendida by hand means calling api.afterbanks.com for its Norma 43, Norma 19, Norma 57, and ID file operations and building each file and form request yourself. Through Jentic you install once, import the Afterbanks API Extendida from the API Directory, store any required credential once, and your agent calls it.
- **Permission scoping:** The Afterbanks API Extendida takes its targets in the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as requesting available Norma 43 files or reading a file form. Every operation the agent can run is one you have added to its allowed set.
- **Credential handling:** Any Afterbanks API Extendida credential 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 'get available Norma 43 files from today to a given date', and Jentic returns the matching Afterbanks API Extendida operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the Afterbanks API Extendida use?

The Afterbanks API Extendida uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I ficheros norma 43 disponibles desde el día actual hasta una fecha dada. with the Afterbanks API Extendida?

Yes. Use the POST /Files endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Afterbanks API Extendida?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I ficheros norma 43 disponibles desde el día actual hasta una fecha dada. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'ficheros norma 43 disponibles desde el día actual hasta una fecha dada.'. Jentic returns the matching Afterbanks API Extendida operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Afterbanks API Extendida have?

The Afterbanks API Extendida exposes 30 endpoints covering batch, categorization, directdebits operations.

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

Yes. Because Jentic One is self-hosted, you decide which Afterbanks API Extendida operations your agent may call, so you can add only the ones it needs, such as requesting available Norma 43 files or reading a file form, and leave everything else out. The API takes its targets in the request body rather than the URL path, so scoping is done per operation: every operation the agent can run is one you have explicitly added to its allowed set. Any required credential is stored once, encrypted by your own instance, and injected at execution time, so the agent never sees raw secrets. This means an agent set up to read file forms cannot post Norma 19 or Norma 57 files unless you grant those operations.