canonical: https://jentic.com/apis/swaggerhub.asig/bank-contact-v2

# Asig Bank Contact V2

Afinis is a diverse group of organizations working to support advancement and use of API standardization in the financial services industry. Utilization of this API requires a developer to [register](https://www.afinis.org/user/register) their application. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically allow a fi to input data into the fi contact data base, allow a fi to retrieve data from the fi contact data base. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Allow a FI to input data into the FI contact data base
- Manage crm data programmatically
- Integrate Bank Contact V2 into automated workflows
- Query and filter Bank Contact V2 records by parameters
- Monitor Bank Contact V2 operational status and events

## Use cases

### CRM Operations

Use the Bank Contact V2 to perform crm operations programmatically. The API provides 2 endpoints covering core functionality including allow a fi to input data into the fi contact data base, allow a fi to retrieve data from the fi contact data base.

Example prompt: Call POST /banks/contact to allow a fi to input data into the fi contact data base

### Data Retrieval and Monitoring

Query Bank Contact V2 resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Bank Contact V2 endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Bank Contact V2 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 apiKey tokens manually.

Example prompt: Search Jentic for 'allow a fi to input data into the fi contact data base', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /banks/contact | Allow a FI to input data into the FI contact data base |
| GET | /banks/contact | Allow a FI to retrieve data from the FI contact data base |

## Key resources

- **Banks** — Operations for banks

## Why Jentic

- **Setup:** Wiring Bank Contact V2 by hand means placing its apikey in the query string on every call and resolving the versioned api.afinis.org base path yourself. Through Jentic you install once, import Bank Contact V2 from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The contact data for this API travels in the request body, not the URL path, so scope by operation: limit the agent to the operations it needs, such as reading bank contact data, and leave the write operation out. You choose the operations it may call, so submitting contact data is not included unless you add it.
- **Credential handling:** Your Bank Contact V2 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 'read a financial institution's contact data' or 'submit bank contact details', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Bank Contact V2 use?

The Bank Contact V2 uses an API key passed in the `apikey` query. 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 allow a fi to input data into the fi contact data base with the Bank Contact V2?

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

### What are the rate limits for the Bank Contact V2?

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 allow a fi to input data into the fi contact data base through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'allow a fi to input data into the fi contact data base'. Jentic returns the matching Bank Contact V2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bank Contact V2 have?

The Bank Contact V2 exposes 2 endpoints covering banks operations.

### Can I limit what my agent is allowed to do with the Bank Contact V2 API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call and which credentials it may use. Since the Bank Contact V2 API has just two operations, you can allow the agent to read contact data with GET /banks/contact while leaving the write operation, POST /banks/contact, out, so it cannot submit new bank contact records unless you explicitly add that operation. Your API key stays under your control and is injected only for the operations you permit.