Igtbdigital Alerts
Browse all Swaggerhub Igtbdigital APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitynone1 EndpointsREST
For Agents
Programmatically raisealert. Covers 1 operations.
Use for: I need to raisealert, Find available developer tools operations, Get the current status of Alerts resources, List all records from Alerts
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
This API is to be used to emit an Alert event to the Alert engine by any alert services consumting consuming application. The API exposes 1 endpoints.
Install Jentic One Beta
Connect the Alerts to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alerts, 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 Alerts API.
raisealert
Manage developer tools data programmatically
Integrate Alerts into automated workflows
Query and filter Alerts records by parameters
Monitor Alerts operational status and events
Use Cases
Patterns agents use Alerts API for, with concrete tasks.
★ Developer Tools Operations
Use the Alerts to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including raisealert.
Call POST /v1/common/raisealert to raisealert
Data Retrieval and Monitoring
Query Alerts 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 Alerts endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Alerts 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 'raisealert', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — this api is to be used to emit an alert event to the alert engine by any alert services consumting consuming application.
METHOD
PATH
DESCRIPTION
POST
/v1/common/raisealert
raisealert
POST
/v1/common/raisealert
raisealert
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Alerts 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., 'raisealert') and Jentic returns the matching Alerts operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Alerts 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 Alerts API through Jentic.
What authentication does the Alerts use?
The Alerts 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 raisealert with the Alerts?
Yes. Use the POST /v1/common/raisealert endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Alerts?
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 raisealert through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'raisealert'. Jentic returns the matching Alerts operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Alerts have?
The Alerts exposes 1 endpoints covering raise alerts operations.
GET STARTED