Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

incident.io (BYOK) — connector documentation

  • MCP endpoint: https://byok-incidentio.connectorbay.com/mcp
  • REST API: POST https://byok-incidentio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-incidentio.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own incident.io incident.io API key (Settings > API keys; view scopes are enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-incidentio.connectorbay.com/health · Tool schemas: https://byok-incidentio.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-incidentio · agent@connectorbay.com

What incident.io (BYOK) is for

incident.io (BYOK) lets an AI assistant read your own incident.io data through the incident.io API with a key you supply (incident.io API key (Settings > API keys; view scopes are enough)). Read-only: 12 tools (list_incidents, get_incident, list_incident_updates, list_severities, list_incident_statuses, list_incident_roles, list_incident_types, list_actions, list_follow_ups, list_users, list_schedules, list_alerts). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.incident.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by incident.io. incident.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What incidents are live in incident.io right now?"
  • "Show the details of incident.io incident 01FCNDV6P870EA6S7TK1DSYDG0"
  • "What updates were posted on incident 01FCNDV6P870EA6S7TK1DSYDG0?"
  • "What severity levels does incident.io have?"
  • "What incident statuses are configured in incident.io?"
  • "Which incident roles are defined in incident.io?"

What it does

  • list_incidents: List incidents (newest first by default) with reference, name, summary, link, status and category, severity, type and timestamps. Filter by status category, severity ids or creation date; cursor-paged.
  • get_incident: Get one incident by id with name, summary, status, severity, type, role assignments, timestamps and links.
  • list_incident_updates: List incident updates (status posts) with message, new status and severity and who posted it, optionally for one incident; cursor-paged.
  • list_severities: List the severity levels with name, description and rank.
  • list_incident_statuses: List the incident statuses with name, category (triage, live, learning, paused, closed, declined, canceled, merged) and rank.
  • list_incident_roles: List incident roles (for example lead and reporter) with name, short form, type and instructions.
  • list_incident_types: List incident types with name, description, default flag and whether they start in triage.
  • list_actions: List incident actions (tasks) with description, status (outstanding, completed, deleted, not_doing), assignee and completion time, optionally for one incident.
  • list_follow_ups: List follow-ups with title, status, priority, assignee, labels and completion time, optionally for one incident or one assignee team.
  • list_users: List users with name, email, role, whether active and Slack id; filter by email; cursor-paged.
  • list_schedules: List on-call schedules with name, time zone, team ids, who is on call now and rotations. Upcoming shifts are included only for page sizes of 25 or less.
  • list_alerts: List alerts with title, status (firing or resolved), description, source link, tags and times; filter by status or creation time; cursor-paged.

BYOK key

You bring your own incident.io incident.io API key (Settings > API keys; view scopes are enough) (https://docs.incident.io/api-reference/incidents-v2/list). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.incident.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the incident.io API (api.incident.io) with a BYOK key; documentation: https://docs.incident.io/api-reference/incidents-v2/list. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by incident.io. incident.io and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your incident.io account.

Built for: Worldwide. Languages: English.