Igtbdigital Alert Packages
Browse all Swaggerhub Igtbdigital APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registrynone1 EndpointsREST
For Agents
Programmatically returns list of available alert packages. Covers 1 operations.
Use for: I need to returns list of available alert packages, Find available developer tools operations, Get the current status of Alert Packages resources, List all records from Alert Packages
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Fetch alert packages for customer onboarding. The API exposes 1 endpoints.
Install Jentic One Beta
Connect the Alert Packages to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alert Packages, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Alert Packages API.
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
Patterns agents use Alert Packages API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'returns list of available alert packages', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — fetch alert packages for customer onboarding.
METHOD
PATH
DESCRIPTION
GET
/v1/common/customeralertpackages/{bankEntityId}
returns list of available alert packages
GET
/v1/common/customeralertpackages/{bankEntityId}
returns list of available alert packages
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Alert Packages none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'returns list of available alert packages') and Jentic returns the matching Alert Packages operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Alert Packages integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Alert Packages API through Jentic.
What authentication does the Alert Packages use?
The Alert Packages uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED