Zenduty
Zenduty is an incident management and on-call platform that orchestrates alert routing, escalation policies, on-call schedules, and incident response workflows for SRE and DevOps teams. The platform integrates with observability tools, ticketing systems, and chat platforms to centralize incident triage. Zenduty exposes a REST API for managing incidents, services, teams, schedules, and escalation policies, plus an Events API for ingesting alerts, all secured with Token authentication.
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 Zenduty the way a machine reads it — 39 machine-readable artifacts across 34 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 — Zenduty scores 32.5/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 Zenduty
Each block below is one kind of artifact we hold for Zenduty. 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 34
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.
Zenduty REST API
Management REST API for incidents, services, teams, users, schedules, escalation policies, and integrations. Authenticated via "Authorization: Token
Zenduty Events API
Alert ingestion API for sending incident events from monitoring, observability, and custom systems into Zenduty.
Zenduty Account Custom Role API
This object represents a custom role of the account. Each custom role object has custom permissions, which the account admin can set from account level permissions and assign th...
Zenduty Account Member API
This object represents a user of the account. Each account member object has a role, which can be owner, admin, or user. Each account has a single owner, but the admins and user...
Zenduty Alert Rules API
Alert Rules in Zenduty are advanced conditions for incoming alerts. They dictate how Zenduty handles alerts and their incidents upon receipt, altering behavior and routing based...
Zenduty Analytics API
These endpoints provide incident analytics for your account. All analytics endpoints accept POST requests with optional filter parameters and return metrics such as incident cou...
Zenduty Contact Methods API
This object represents one of the following communication channels(Email, SMS, Phone Call, Slack, Microsoft Team, Google Chat). A user can add multiple contacts methods.
Zenduty Escalation Policies API
This object represents the escalation policy of a team. You can checkout the escalation policy docs here https://docs.zenduty.com/docs/escalationpolicies
Zenduty Events API
This object represents the events of an integration.
Zenduty Forwarding Rules API
This object represents a user's forwarding rules. A user can forward his notifications to the other account members in case an incident occurs.
Zenduty Global Router API
This object represents the Global Router of the Account. You can checkout the global alert routing docs here https://docs.zenduty.com/docs/globalalertrouting
Zenduty Global Router Rules API
The Rules of the Global Router in an Account are represented by this object. Visit this link to view the documentation for the global alert routing rules https://docs.zenduty.co...
Zenduty Incident Alerts API
This object represents the incident alerts of an incident.
Zenduty Incident Notes API
This object represents the incident notes of an incident.
Zenduty Incident Responders API
This object represents the incident responders of an incident.
Zenduty Incident Roles API
This object represents the incident roles of an incident. You can checkout the incident role docs here https://docs.zenduty.com/docs/incidentroles
Zenduty Incident Tags API
This object represents the incident tags of an incident.
Zenduty Incidents API
This object represents the incidents of the account. You can checkout the incident docs here https://docs.zenduty.com/docs/incidents
Zenduty Integrations API
This object represents the integrations associated with a service. You can checkout the integration docs here https://docs.zenduty.com/docs/integrations
Zenduty Notification Rules API
This object represents a user's notification rules. A user can have notification rules for high urgency and low urgency incidents.
Zenduty OnCall API
This object represents the user who is oncall.
Zenduty Postmortem API
This object represents the postmortem of an incident. You can checkout the postmortem docs here https://docs.zenduty.com/docs/incidentpostmortem
Zenduty Priorities API
This object represents the priority of an incident. You can checkout the priority docs here https://docs.zenduty.com/docs/incidentpriority
Zenduty Schedule Overrides API
This object represents the Override of a Schedule. You can checkout the Schedule Override docs here https://docs.zenduty.com/docs/schedules/#schedule-override
Zenduty Schedules API
This object represents the schedule of a team. You can checkout the schedule docs here https://docs.zenduty.com/docs/schedules
Zenduty Services API
This object represents the services associated with a team. You can checkout the services docs here https://docs.zenduty.com/docs/services
Zenduty SLA API
This object represents the SLA of an incident. You can checkout the SLA docs here https://docs.zenduty.com/docs/incidentsla
Zenduty Tags API
This object represents the tags of an incident. You can checkout the tag docs here https://docs.zenduty.com/docs/incidenttags
Zenduty Task Templates API
This object represents the task templates of the team. You can checkout the task template docs here https://docs.zenduty.com/docs/tasktemplates
Zenduty Team Maintenance Mode API
This object represents the maintenance mode of a team. You can checkout the team maintenance mode docs here https://docs.zenduty.com/docs/maintenancewindows
Zenduty Team Members API
This object represents the users of a team. Each team member has a role which can be a manager or a user. You can checkout the team member docs here https://docs.zenduty.com/doc...
Zenduty Team Permissions API
This object represents the permissions of a team. It lets you access the particular team elements that the team has given permissions to use.
Zenduty Teams API
This object represents a team of the account. It lets you create different independent operational units in the account. You can check out the team docs here https://docs.zendut...
Zenduty User Custom Role API
This object represents a user's custom role. Each user can be assigned to only one custom role.
Scroll within the panel for all 34 ·
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).
Zenduty
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.
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 Zenduty — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/zenduty · machine-readable index on apis.io