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 Schedules API

The Schedules API from ilert — 5 operation(s) for schedules.

ilert Schedules 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 Schedules. 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 9 operations across 5 paths, and defines 12 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.

9 operations 5 paths 12 schemas 1 DELETE5 GET1 POST2 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 Schedules 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 9

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

Schedules 9
GET
/schedules
List on-call schedules.
3 params → 200
POST
/schedules
Create a new on-call schedule.
1 param body → 201
GET
/schedules/{id}
Get the on-call schedule with the specified id.
2 params → 200
PUT
/schedules/{id}
Update an on-call schedule.
2 params body → 200
DELETE
/schedules/{id}
Delete the on-call schedule with the specified id.
1 param → 204
GET
/schedules/{id}/shifts
Get shifts for the specified schedule and date range.
4 params → 200
GET
/schedules/{id}/overrides
Get overrides for the specified schedule.
1 param → 200
PUT
/schedules/{id}/overrides
Add an override shift to a schedule.
1 param body → 200
GET
/schedules/{id}/user-on-call
Get the user (wrapped in a shift object) on-call for the specified schedule.
1 param → 200204

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are User (15 properties), Schedule (11 properties), ScheduleLayerConfig (7 properties), UserRel (3 properties). Each schema is shown below with its type and property counts.

TimeZone
string
TeamRel
object
2 properties
UserRel
object
3 properties 1 required
ShiftRel
object
3 properties
ScheduleLayerConfig
object
7 properties 3 required
Role
string
Schedule
object
11 properties
Shift
object
3 properties
User
object
15 properties 3 required
ScheduleRel
object
3 properties
TimeOfWeek
object
2 properties 2 required
ScheduleLayerRestriction
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ilert-schedules-api-openapi.yml Raw ↑

Other APIs ilert publishes across the network.

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