canonical: https://jentic.com/apis/swaggerhub.igtbdigital/alert-packages

# Igtbdigital Alert Packages

Fetch alert packages for customer onboarding. The API exposes 1 endpoints.

## For AI agents

Programmatically returns list of available alert packages. Covers 1 operations.

## Scope

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

## Capabilities

- returns list of available alert packages
- Manage developer tools data programmatically
- Integrate Alert Packages into automated workflows
- Query and filter Alert Packages records by parameters
- Monitor Alert Packages operational status and events

## Use cases

### Developer Tools Operations

Use the Alert Packages to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including returns list of available alert packages.

Example prompt: Call GET /v1/common/customeralertpackages/{bankEntityId} to returns list of available alert packages

### Data Retrieval and Monitoring

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

### AI Agent Integration via Jentic

AI agents discover and call Alert Packages 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 'returns list of available alert packages', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/common/customeralertpackages/{bankEntityId} | returns list of available alert packages |

## Key resources

- **Alert package for customer onboarding** — Operations related to Alert package for customer onboarding

## Why Jentic

- **Setup:** Wiring the Alert Packages API by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and mapping the alert-package response yourself. Through Jentic you install once, import Alert Packages from the API Directory, and your agent calls it.
- **Permission scoping:** The API puts the bank entity id in the URL path (/v1/common/customeralertpackages/{bankEntityId}), so a rule can pin your agent to one bank entity: it reads that entity's alert packages and nothing else. You choose the operations it may call, so only the read you need is included unless you add more.
- **Credential handling:** This API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available alert packages for a bank entity', and Jentic returns the matching Alert Packages operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Alert Packages use?

The Alert Packages 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 returns list of available alert packages with the Alert Packages?

Yes. Use the GET /v1/common/customeralertpackages/{bankEntityId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Alert Packages?

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 returns list of available alert packages through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns list of available alert packages'. Jentic returns the matching Alert Packages operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Alert Packages have?

The Alert Packages exposes 1 endpoints covering alert package for customer onboarding operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials your agent may use. The only operation here is GET /v1/common/customeralertpackages/{bankEntityId}, and because the bank entity id lives in the URL path, you can pin your agent to a single bank entity so it reads that entity's alert packages and nothing else. You choose which operations are allowed, so the agent gets just that read unless you explicitly add more.