xMatters
xMatters is a service reliability platform that orchestrates intelligent communication, on-call management, and incident response workflows for IT operations, DevOps, and major incident teams. The platform routes signals from monitoring tools to the right people via multiple channels (voice, SMS, push, email, chat) and triggers automated remediation workflows via its integration builder and Flow Designer. The xMatters REST API provides full programmatic control over people, groups, on-call schedules, events, scenarios, and integrations using Basic auth, API keys, or OAuth 2.0.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles xMatters the way a machine reads it — 17 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — xMatters scores 33.7/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile xMatters
Each block below is one kind of artifact we hold for xMatters. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
xMatters REST API
REST API for managing people, groups, devices, on-call schedules, events, conferences, scenarios, sites, and integrations in xMatters. The base URL identifies the customer insta...
xMatters Devices API
The Devices API from xMatters — 2 operation(s) for devices.
xMatters Events API
The Events API from xMatters — 3 operation(s) for events.
xMatters Groups API
The Groups API from xMatters — 3 operation(s) for groups.
xMatters Integrations API
The Integrations API from xMatters — 1 operation(s) for integrations.
xMatters OnCall API
The OnCall API from xMatters — 1 operation(s) for oncall.
xMatters People API
The People API from xMatters — 4 operation(s) for people.
xMatters Plans API
The Plans API from xMatters — 2 operation(s) for plans.
xMatters Scenarios API
The Scenarios API from xMatters — 1 operation(s) for scenarios.
xMatters Services API
The Services API from xMatters — 1 operation(s) for services.
xMatters Shifts API
The Shifts API from xMatters — 1 operation(s) for shifts.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
xMatters REST API
OPEN COLLECTIONSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for xMatters — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/xmatters · machine-readable index on apis.io