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

Datadog Incidents (BYOK) — connector documentation

  • MCP endpoint: https://byok-datadog-incidents.connectorbay.com/mcp
  • REST API: POST https://byok-datadog-incidents.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-datadog-incidents.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Datadog Incidents Datadog API key (US1 site, datadoghq.com), sent in the X-Upstream-Key header and the Datadog application key (needs the incident_read scope) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-datadog-incidents.connectorbay.com/health · Tool schemas: https://byok-datadog-incidents.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-datadog-incidents · agent@connectorbay.com

What Datadog Incidents (BYOK) is for

Datadog Incidents (BYOK) lets an AI assistant read your own Datadog Incidents data through the Datadog Incidents API with a key you supply (Datadog API key (US1 site, datadoghq.com)). Read-only: 9 tools (list_incidents, get_incident, list_incident_impacts, list_incident_attachments, list_incident_todos, list_incident_types, list_incident_user_defined_fields, list_incident_impact_fields, list_postmortem_templates). 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.datadoghq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Datadog Incidents. Datadog Incidents 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:

  • "Which Datadog incidents are active right now?"
  • "Show the details of Datadog incident 00000000-0000-0000-0000-000000000001"
  • "What impacts were recorded for Datadog incident 00000000-0000-0000-0000-000000000001?"
  • "Is there a postmortem attached to Datadog incident 00000000-0000-0000-0000-000000000001?"
  • "What follow-up to-dos does Datadog incident 00000000-0000-0000-0000-000000000001 have?"
  • "Which incident types are configured in Datadog?"

What it does

  • list_incidents: List incidents with title, severity, state, key timestamps, customer impact and time-to-detect, repair and resolve (seconds). Newest page first; page with page_offset.
  • get_incident: Get one incident by UUID: title, severity, state, fields, timeline timestamps, customer impact and durations.
  • list_incident_impacts: List the customer or service impacts recorded for an incident: type, description, start and end time.
  • list_incident_attachments: List an incident's attachments: postmortem documents and links with title and URL. Filter by attachment type.
  • list_incident_todos: List an incident's remediation to-dos with content, completion time and due date. Assignees are left out.
  • list_incident_types: List incident types with name, prefix, description and whether each is the default.
  • list_incident_user_defined_fields: List the custom fields of incidents (dropdown, textbox, multiselect, number) with name, display name, tag key, required flag and allowed values.
  • list_incident_impact_fields: List the impact fields incidents can record (name, display name, type, choices).
  • list_postmortem_templates: List postmortem templates with name, storage location (confluence, google docs, notebook) and default flag. Template bodies are left out.

BYOK key

You bring your own Datadog Incidents Datadog API key (US1 site, datadoghq.com) (https://app.datadoghq.com/organization-settings/api-keys). 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.datadoghq.com 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 Datadog Incidents API (api.datadoghq.com) with a BYOK key; documentation: https://docs.datadoghq.com/api/latest/incidents/. 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 Datadog Incidents. Datadog Incidents 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 Datadog Incidents account.

Built for: Worldwide. Languages: English.