How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ilert Alert Actions API

The Alert Actions API from ilert — 3 operation(s) for alert actions.

ilert Alert Actions API is one of 33 APIs that ilert publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Alert Actions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, and 1 JSON Schema.

This API exposes 7 operations across 3 paths, and defines 61 schemas. It is described by OpenAPI 3.2.0, at version v2.2026.5-r.3.

Requests are made against a single base URL, /api.

7 operations 3 paths 61 schemas 1 DELETE3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2.2026.5-r.3
Base URL
https://api.ilert.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

ilert Alert Actions API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey). By default, every request must be authenticated.

  • apiKey — The Bearer API key of your user more info .

Paths & Operations 7

Across 3 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Alert Actions 7
GET
/alerts/{id}/actions
Get available actions for specified alert.
1 param → 200
POST
/alerts/{id}/actions
Invoke a specific alert action.
1 param body → 201
GET
/alert-actions
Get alert actions.
4 params → 200
POST
/alert-actions
Create a new alert action.
body → 200
GET
/alert-actions/{id}
Get a specific alert action.
2 params → 200
PUT
/alert-actions/{id}
Update the specific alert action. (note: type cannot be changed)
1 param body → 200
DELETE
/alert-actions/{id}
Remove a specific alert action.
1 param → 204

Schemas 61

The contract defines 61 schemas that model the data the API accepts and returns. The most detailed are AlertSource (38 properties), AlertAction (16 properties), User (15 properties), Service (11 properties). Each schema is shown below with its type and property counts.

AlertSourceSeverityTemplateMapping
object
2 properties 2 required
SupportHourException
object
4 properties 4 required
AlertSourceTemplateElementArg
object
2 properties
ServiceStatus
string
the service status
EscalationPolicy
object
8 properties 2 required
UserRel
object
3 properties 1 required
CParamsAWSLambda
object
2 properties
CParamsAutotask
object
7 properties 1 required
TimeZone
string
CParamsServiceNow
object
9 properties
ScheduleRel
object
3 properties
AlertSourceLinkTemplate
object
2 properties 2 required
CParamsZapier
object
1 property
CParamsDingTalk
object
2 properties
CParamsDiscord
object
CParamsEmail
object
3 properties
CParamsGoogleChat
object
2 properties 1 required
CParamsTopdesk
object
1 property
SupportDay
object
2 properties 2 required
CParamsDingTalkAction
object
4 properties
AlertSourcePriorityTemplate
object
2 properties 2 required
CParamsAutomationRule
object
6 properties 3 required
CParamsGithub
object
3 properties
AlertPriorityRule
string
AlertSourceSeverityTemplate
object
2 properties 2 required
CParamsZoomMeeting
object
1 property
CParamsWebhook
object
3 properties 1 required
CParamsMicrosoftTeamsWebhookOnly
object
ServiceUptimePercentage
object
1 property
ServiceOutage
object
3 properties
CParamsSysdig
object
2 properties
CParamsDatadog
object
3 properties
Service
object
11 properties
IncidentStatus
string
the incident status
CParamsStatusPageIO
object
1 property
CParamsJira
object
3 properties
AlertActionResult
object
6 properties
AlertSourceTemplateElement
object
4 properties
User
object
15 properties 3 required
TeamRel
object
2 properties
CParamsMicrosoftTeams
object
5 properties 2 required
AlertSource
object
38 properties 3 required
SupportHour
object
6 properties 3 required
IncidentNoIncludes
object
9 properties
AlertActionType
string
ServiceNoIncludes
object
8 properties
AlertAction
object
16 properties 2 required
CParamsTelegram
object
1 property 1 required
CParamsZoomChat
object
1 property
AlertSourceTemplate
object
2 properties
AlertActionTrigger
object
6 properties
ServiceUptime
object
4 properties
EscalationRule
object
7 properties 1 required
CParamsAzureFunction
object
2 properties
IntegrationType
string
AlertSourcePriorityTemplateMapping
object
2 properties 2 required
CParamsSlack
object
4 properties 1 required
CParamsGoogleFunction
object
2 properties
CParamsGoogleChatWebhookOnly
object
Role
string
CParamsZendesk
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ilert-alert-actions-api-openapi.yml Raw ↑

Other APIs ilert publishes across the network.

ilert Alert Sources API
ilert Alerts API
ilert Call Flow Numbers API
ilert Call Flows API
ilert Connectors API
ilert Contacts API
ilert Deployment Events API
ilert Deployment Pipelines API
ilert Escalation Policies API
ilert Event Flows API
ilert Events API
ilert Heartbeat Monitors API
Where this information came from

This is an independent, third-party profile of ilert Alert Actions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.