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

Moogsoft On-Call API

This API allows you to save and retrieve on-call schedules, escalation policies

Moogsoft On-Call API is one of 17 APIs that Moogsoft publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AIOps, Incident Management, Notification Policies, on-call open issues, and on-call schedule occurrences. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 22 operations across 13 paths, organized into 4 resource areas, and defines 30 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.moogsoft.ai, https://api.dev.moogsoft.cloud.

22 operations 13 paths 30 schemas 3 DELETE10 GET3 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.moogsoft.ai
Authentication
API Key
Terms of Service
Resource Areas
4

Authentication & Security 1

Moogsoft On-Call API declares 1 security scheme for authenticating requests. An API key is passed in the header as apiKey (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API Key for accessing On-Call API

Paths & Operations 22

Across 13 paths, the API surfaces 22 operations — 3 DELETE, 10 GET, 3 PATCH, 6 POST. They span 4 resource areas: Acknowledge Resource, on-call schedules, notification policies, on-call schedule occurrences. Each is listed below with its method, path, parameters, and response codes.

Acknowledge Resource 3
GET
/v1/on-call/ack/{incidentId}
Acknowledge Incident
acknowledgeIncidentAlt 2 params → 2004004044XX5XX
POST
/v1/on-call/ack/{incidentId}
Acknowledge Incident
acknowledgeIncident 2 params body → 2014004044XX5XX
POST
/v1/on-call/ack
Acknowledge Incidents
acknowledgeIncidents 1 param body → 2014004044XX5XX
on-call schedules 13

on-call scheduling

GET
/v1/on-call/schedules/{id}/previewdeprecated
Gets the final on-call scheduled occurrences based on start and end timestamps.
getSchedulePreviewAlt 3 params → 2004004044XX5XX
GET
/v1/on-call/schedules/{id}/occurrences/ready
Gets active and pending occurrences for the schedule
getActiveAndPending 3 params → 2004004044XX5XX
GET
/v1/on-call/schedules
Retrieves all, existing on-call schedules.
getSchedules 5 params → 2004004044XX5XX
POST
/v1/on-call/schedules
Creates a new on-call schedule.
createSchedule body → 2004004044XX5XX
POST
/v1/on-call/schedules/preview
Gets the final on-call scheduled occurrences based on start and end timestamps
getFinalSchedulePreview 3 params body → 2004004044XX5XX
GET
/v1/on-call/schedules/{id}/overrides
Gets list of Overrides
getOverrides 3 params → 2004004044XX5XX
POST
/v1/on-call/schedules/{id}/overrides
Creates an Override
createOverrides 1 param body → 2014004044XX5XX
GET
/v1/on-call/schedules/{id}/active-user
Gets the user currently on call for a schedule
getCurrentOnCallUser 1 param → 2004004044XX5XX
PATCH
/v1/on-call/schedules/{id}
Updates an existing on-call schedule.
updateSchedule 1 param body → 2004004044XX5XX
GET
/v1/on-call/schedules/{id}
Retrieves the existing on-call schedule.
getSchedule 1 param → 2004004044XX5XX
DELETE
/v1/on-call/schedules/{id}
Deletes an existing on-call schedule.
deleteSchedule 1 param → 2044004044XX5XX
GET
/v1/on-call/schedules/{id}/occurrences
Gets all occurrences for the schedule
getScheduleOccurrences 3 params → 2004004044XX5XX
DELETE
/v1/on-call/occurrences/{id}/overrides
Deletes an Override
deleteOverrides 1 param → 2044004044XX5XX
notification policies 5

notification policies for on-call

GET
/v1/on-call/notification-policy
Retrieves all, existing on-call notification policies.
getNotificationPolicies 4 params → 2004004044XX5XX
POST
/v1/on-call/notification-policy
creates a new on-call notification policy.
createNotificationPolicy body → 2004004044XX5XX
PATCH
/v1/on-call/notification-policy/{id}
Updates an existing on-call notification policy.
updateNotificationPolicy 1 param body → 2004004044XX5XX
GET
/v1/on-call/notification-policy/{id}
Retrieves an existing on-call notification policy.
getNotificationPolicy 1 param → 2004004044XX5XX
DELETE
/v1/on-call/notification-policy/{id}
Deletes an existing on-call notification policy.
deleteNotificationPolicy 1 param → 2044004044XX5XX
on-call schedule occurrences 1

on-call occurrence scheduling

PATCH
/v1/on-call/occurrences/{id}/overrides
Edits an Override
editOverrides 1 param body → 2044004044XX5XX

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are ScheduleDto (15 properties), ScheduleOccurrenceDto (11 properties), NotificationPolicyDto (10 properties), BaseScheduleDto (9 properties). Each schema is shown below with its type and property counts.

MoogFailureResponse
object
On-Call API failure response body
3 properties 2 required
MoogErrorResponse
object
On-Call API error response body
3 properties 2 required
AckPayloadDto
object
4 properties 3 required
MoogResponseFinalScheduleDto
object
On-Call API FinalScheduleDto response body
2 properties 2 required
FinalScheduleDto
object
Definition for a specific occurrence of an on-call schedule
2 properties
ScheduleOccurrenceDto
object
Definition for a specific occurrence of an on-call schedule
11 properties 3 required
Timestamp
integer
Number of milliseconds since Jan 1, 1970 UTC
OnCallStatus
string
OnCall Occurrence Status
MoogResponseScheduleOccurrenceListDto
object
On-Call API ScheduleOccurrenceListDto response body
2 properties 2 required
ScheduleOccurrenceListDto
object
Definition for a list of on-call schedule occurrences
2 properties
MoogResponseScheduleListDto
object
On-Call API ScheduleListDto response body
2 properties 2 required
ScheduleListDto
object
2 properties
ScheduleDto
object
definition for creating or updating a given on-call schedule
15 properties 5 required
ScheduleUserDto
object
2 properties 2 required
Rotation
object
2 properties 2 required
RotationType
string
On-call scheduling rotation type
Handoff
object
2 properties 1 required
DayOfWeek
string
Day of Week
Restriction
object
5 properties 3 required
RestrictionType
string
Type of Restriction on a Schedule
BaseScheduleDto
object
definition for creating or updating a given on-call schedule
9 properties 5 required
MoogResponseScheduleDto
object
On-Call API ScheduleDto response body
2 properties 2 required
MoogResponseNotificationPolicyListDto
object
On-Call API NotificationPolicyListDto response body
2 properties 2 required
NotificationPolicyListDto
object
2 properties
NotificationPolicyDto
object
10 properties 3 required
NotificationAction
object
1 property
BaseNotificationPolicyDto
object
A notification policy for paging a set of on-call schedules
5 properties 3 required
MoogResponseNotificationPolicyDto
object
On-Call API NotificationPolicyDto response body
2 properties 2 required
BaseScheduleOccurrenceDto
object
base definition for a schedule occurrence
3 properties 3 required
BulkAckPayloadDto
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moogsoft-incident-responder-openapi.yaml Raw ↑

Other APIs Moogsoft publishes across the network.

Moogsoft Alerts/Incidents API
Moogsoft Azure Application Insights API
Moogsoft Create Your Own Integration API
Moogsoft Amazon CloudWatch API
Moogsoft Collector V2 API
Moogsoft Config API
Moogsoft Events Integration API
Moogsoft Rollup Service API
Moogsoft Metrics API
Moogsoft PagerDuty Integration API
Moogsoft Probable Root Cause API
Moogsoft Similar Incidents API
Where this information came from

This is an independent, third-party profile of Moogsoft On-Call 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.