Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ilert Alerts API

The Alerts API from ilert — 11 operation(s) for alerts.

ilert Alerts 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 Alerts. 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 12 operations across 11 paths, and defines 42 schemas. It is described by OpenAPI 3.0.1, at version v2.2026.5-r.3.

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

12 operations 11 paths 42 schemas 1 DELETE6 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

ilert Alerts 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 12

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

Alerts 12
GET
/alerts
List alerts (optionally matching certain criteria that are specified by query parameters).
9 params → 200
POST
/alerts
Create alerts with customised parameters without requiring events from monitoring tools that use our Events API.
body → 201
GET
/alerts/count
Get the alert count matching the specified criteria.
5 params → 200
GET
/alerts/{id}
Get the alert with the specified id.
2 params → 200
GET
/alerts/{id}/suggested-responders
Get available (assignable) responders for the alert with the specified id.
2 params → 200
POST
/alerts/{id}/responders
Add an additional responder to the alert.
1 param → 201404405
DELETE
/alerts/{id}/responders/{user-id}
Remove a responder from the alert.
2 params → 204404
PUT
/alerts/{id}/assign
Assign the alert.
4 params → 200
PUT
/alerts/{id}/accept
Accept the Alert.
1 param → 200
PUT
/alerts/{id}/resolve
Resolve the alert.
1 param → 200
GET
/alerts/{id}/notifications
Get notifications for the specified alert.
1 param → 200
GET
/alerts/{id}/log-entries
Get log entries for the specified alert.
6 params → 200

Schemas 42

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

ServiceStatus
string
the service status
IntegrationType
string
EscalationRule
object
7 properties 1 required
SimpleIdField64
object
For POST and PUT requests only the id field is required for sub entities, e.g. status page - service, alert source - support hour
1 property 1 required
LogFilterType
string
AlertSource
object
38 properties 3 required
SupportHour
object
6 properties 3 required
Alert
object
24 properties
IncidentNoIncludes
object
9 properties
AlertSourceTemplate
object
2 properties
AlertSourceSeverityTemplateMapping
object
2 properties 2 required
Notification
object
9 properties
UserRel
object
3 properties 1 required
AlertSourcePriorityTemplate
object
2 properties 2 required
SupportHourException
object
4 properties 4 required
ServiceOutage
object
3 properties
ScheduleRel
object
3 properties
AlertPriorityRule
string
AlertPriority
string
ServiceNoIncludes
object
8 properties
AlertSourceTemplateElement
object
4 properties
IncidentStatus
string
the incident status
Service
object
11 properties
AlertSourcePriorityTemplateMapping
object
2 properties 2 required
Role
string
AlertResponder
object
3 properties
User
object
15 properties 3 required
SupportDay
object
2 properties 2 required
ServiceUptime
object
4 properties
EventImage
object
3 properties
EscalationPolicy
object
8 properties 2 required
LogEntry
object
7 properties
SuggestedResponder
object
4 properties
TeamRel
object
2 properties
AlertSourceSeverityTemplate
object
2 properties 2 required
ServiceUptimePercentage
object
1 property
ManualAlert
object
9 properties 2 required
AlertSourceTemplateElementArg
object
2 properties
CountResponse
object
1 property
AlertSourceLinkTemplate
object
2 properties 2 required
EventLink
object
2 properties
TimeZone
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ilert-alerts-api-openapi.yml Raw ↑

Other APIs ilert publishes across the network.

ilert Alert Actions API
ilert Alert Sources 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