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

# Asig Bank Contacts APIs

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 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically financial institution contact information for fraud or operational issues. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Financial institution contact information for fraud or operational issues
- Manage crm data programmatically
- Integrate Bank Contacts APIs into automated workflows
- Query and filter Bank Contacts APIs records by parameters
- Monitor Bank Contacts APIs operational status and events

## Use cases

### CRM Operations

Use the Bank Contacts APIs to perform crm operations programmatically. The API provides 1 endpoints covering core functionality including financial institution contact information for fraud or operational issues.

Example prompt: Call GET /banks/{bank_id}/contact to financial institution contact information for fraud or operational issues

### Data Retrieval and Monitoring

Query Bank Contacts APIs 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 Contacts APIs endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Bank Contacts APIs 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 'financial institution contact information for fraud or operational issues', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /banks/{bank_id}/contact | Financial institution contact information for fraud or operational issues |

## Key resources

- **Banks** — Operations for banks

## Why Jentic

- **Setup:** Wiring the Bank Contacts APIs by hand means placing its apikey in the query string on every call against the api.afinis.org host and tracking the bank id path yourself. Through Jentic you install once, import the Bank Contacts APIs from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the bank id in the URL path (/banks/{bank_id}/contact), so a rule can pin your agent to one bank: it can read that bank's contact information and nothing else. You choose the operations it may call, so it reads only what you allow it to reach.
- **Credential handling:** Your Bank Contacts 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 'get a bank's contact information for fraud or operational issues', 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 Contacts APIs use?

The Bank Contacts APIs 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 financial institution contact information for fraud or operational issues with the Bank Contacts APIs?

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

### What are the rate limits for the Bank Contacts APIs?

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 financial institution contact information for fraud or operational issues through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'financial institution contact information for fraud or operational issues'. Jentic returns the matching Bank Contacts APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bank Contacts APIs have?

The Bank Contacts APIs exposes 1 endpoints covering banks operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API only exposes GET /banks/{bank_id}/contact, and the bank id lives in the URL path, so you can pin the agent to a single bank so it reads that one institution's contact details and nothing else. You choose the operations it may call, keeping it read-only and scoped to exactly the banks you allow.