productivity
incident.io MCP, CLI, and Lua Integration for AI Agents
incident.io integration docs for AI agents: MCP gateway setup, incident.io CLI commands, Lua API reference, credentials, and function schemas.incident.io for agents
Credentials can be configured manually in web or CLI hosts.
Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.
Agent Surfaces
Machine-Readable Metadata
Function Catalog
| Function | Type | Parameters | Description |
|---|---|---|---|
incident-io.incident_io_actions_v1_list | Read read | 0 | List Actions V1 Official incident.io endpoint: GET /v1/actions List all actions for an organisation. |
incident-io.incident_io_actions_v1_show | Read read | 0 | Show Actions V1 Official incident.io endpoint: GET /v1/actions/{id} Get a single incident action. |
incident-io.incident_io_api_keys_v1_list | Read read | 0 | List API Keys V1 Official incident.io endpoint: GET /v1/api_keys List API keys visible to the calling API key, with pagination. An API key with account-level `api_keys_manage` access will see all keys, while a key with the `api_keys_manage` |
incident-io.incident_io_api_keys_v1_create | Write write | 0 | Create API Keys V1 Official incident.io endpoint: POST /v1/api_keys Create a new API key. The calling API key can only assign roles whose scopes are a subset of its own. The `api_keys_manage` role cannot be assigned via the API. An organiza |
incident-io.incident_io_api_keys_v1_show | Read read | 0 | Show API Keys V1 Official incident.io endpoint: GET /v1/api_keys/{id} Show details of a specific API key, including its roles, team assignments and when its token was last issued. This endpoint requires a valid API key with the `api_keys_ma |
incident-io.incident_io_api_keys_v1_update | Write write | 0 | Update API Keys V1 Official incident.io endpoint: PUT /v1/api_keys/{id} Update an existing API key's name, roles, or team assignments. All fields must be provided (PUT semantics). The calling API key can only assign roles whose scopes are a |
incident-io.incident_io_api_keys_v1_delete | Write write | 0 | Delete API Keys V1 Official incident.io endpoint: DELETE /v1/api_keys/{id} Delete an existing API key. The calling API key does not need to hold the scopes of the key being deleted, but a team-scoped key can only delete keys belonging to it |
incident-io.incident_io_api_keys_v1_rotate | Write write | 0 | Rotate API Keys V1 Official incident.io endpoint: POST /v1/api_keys/{id}/actions/rotate Rotate the access token for an API key. This generates a new bearer token and optionally keeps the old token valid for a configurable grace period (up t |
incident-io.incident_io_custom_field_options_v1_list | Read read | 0 | List Custom Field Options V1 Official incident.io endpoint: GET /v1/custom_field_options Show custom field options for a custom field |
incident-io.incident_io_custom_field_options_v1_create | Write write | 0 | Create Custom Field Options V1 Official incident.io endpoint: POST /v1/custom_field_options Create a custom field option. If the sort key is not supplied, it'll default to 1000, so the option appears near the end of the list. |
incident-io.incident_io_custom_field_options_v1_show | Read read | 0 | Show Custom Field Options V1 Official incident.io endpoint: GET /v1/custom_field_options/{id} Get a single custom field option |
incident-io.incident_io_custom_field_options_v1_update | Write write | 0 | Update Custom Field Options V1 Official incident.io endpoint: PUT /v1/custom_field_options/{id} Update a custom field option |
incident-io.incident_io_custom_field_options_v1_delete | Write write | 0 | Delete Custom Field Options V1 Official incident.io endpoint: DELETE /v1/custom_field_options/{id} Delete a custom field option |
incident-io.incident_io_custom_fields_v1_list | Read read | 0 | List Custom Fields V1 Official incident.io endpoint: GET /v1/custom_fields List all custom fields for an organisation. |
incident-io.incident_io_custom_fields_v1_create | Write write | 0 | Create Custom Fields V1 Official incident.io endpoint: POST /v1/custom_fields Create a new custom field |
incident-io.incident_io_custom_fields_v1_show | Read read | 0 | Show Custom Fields V1 Official incident.io endpoint: GET /v1/custom_fields/{id} Get a single custom field. |
incident-io.incident_io_custom_fields_v1_update | Write write | 0 | Update Custom Fields V1 Official incident.io endpoint: PUT /v1/custom_fields/{id} Update the details of a custom field |
incident-io.incident_io_custom_fields_v1_delete | Write write | 0 | Delete Custom Fields V1 Official incident.io endpoint: DELETE /v1/custom_fields/{id} Delete a custom field |
incident-io.incident_io_utilities_v1_identity | Read read | 0 | Identity Utilities V1 Official incident.io endpoint: GET /v1/identity Test if your API key is valid, and which roles it has. |
incident-io.incident_io_incident_attachments_v1_list | Read read | 0 | List Incident Attachments V1 Official incident.io endpoint: GET /v1/incident_attachments List all incident attachments for a given external resource or incident. You must provide either a specific incident ID or a specific external resource |
incident-io.incident_io_incident_attachments_v1_create | Write write | 0 | Create Incident Attachments V1 Official incident.io endpoint: POST /v1/incident_attachments Attaches an external resource to an incident |
incident-io.incident_io_incident_attachments_v1_delete | Write write | 0 | Delete Incident Attachments V1 Official incident.io endpoint: DELETE /v1/incident_attachments/{id} Unattaches an external resource from an incident |
incident-io.incident_io_incident_memberships_v1_create | Write write | 0 | Create Incident Memberships V1 Official incident.io endpoint: POST /v1/incident_memberships Makes a user a member of a private incident |
incident-io.incident_io_incident_memberships_v1_revoke | Write write | 0 | Revoke Incident Memberships V1 Official incident.io endpoint: POST /v1/incident_memberships/actions/revoke Revoke a user's membership of a private incident |
incident-io.incident_io_incident_relationships_v1_list | Read read | 0 | List Incident Relationships V1 Official incident.io endpoint: GET /v1/incident_relationships List related incidents for a specific incident. |
incident-io.incident_io_incident_roles_v1_list | Read read | 0 | List Incident Roles V1 Official incident.io endpoint: GET /v1/incident_roles List all incident roles for an organisation. |
incident-io.incident_io_incident_roles_v1_create | Write write | 0 | Create Incident Roles V1 Official incident.io endpoint: POST /v1/incident_roles Create a new incident role |
incident-io.incident_io_incident_roles_v1_show | Read read | 0 | Show Incident Roles V1 Official incident.io endpoint: GET /v1/incident_roles/{id} Get a single incident role. |
incident-io.incident_io_incident_roles_v1_update | Write write | 0 | Update Incident Roles V1 Official incident.io endpoint: PUT /v1/incident_roles/{id} Update an existing incident role |
incident-io.incident_io_incident_roles_v1_delete | Write write | 0 | Delete Incident Roles V1 Official incident.io endpoint: DELETE /v1/incident_roles/{id} Removes an existing role |
incident-io.incident_io_incident_statuses_v1_list | Read read | 0 | List Incident Statuses V1 Official incident.io endpoint: GET /v1/incident_statuses List all incident statuses for an organisation. |
incident-io.incident_io_incident_statuses_v1_create | Write write | 0 | Create Incident Statuses V1 Official incident.io endpoint: POST /v1/incident_statuses Create a new incident status |
incident-io.incident_io_incident_statuses_v1_show | Read read | 0 | Show Incident Statuses V1 Official incident.io endpoint: GET /v1/incident_statuses/{id} Get a single incident status. |
incident-io.incident_io_incident_statuses_v1_update | Write write | 0 | Update Incident Statuses V1 Official incident.io endpoint: PUT /v1/incident_statuses/{id} Update an existing incident status |
incident-io.incident_io_incident_statuses_v1_delete | Write write | 0 | Delete Incident Statuses V1 Official incident.io endpoint: DELETE /v1/incident_statuses/{id} Delete an incident status |
incident-io.incident_io_incident_types_v1_list | Read read | 0 | List Incident Types V1 Official incident.io endpoint: GET /v1/incident_types List all incident types for an organisation. |
incident-io.incident_io_incident_types_v1_show | Read read | 0 | Show Incident Types V1 Official incident.io endpoint: GET /v1/incident_types/{id} Get a single incident type. |
incident-io.incident_io_incidents_v1_list | Read read | 0 | List Incidents V1 Official incident.io endpoint: GET /v1/incidents List all incidents for an organisation. |
incident-io.incident_io_incidents_v1_create | Write write | 0 | Create Incidents V1 Official incident.io endpoint: POST /v1/incidents Create a new incident. |
incident-io.incident_io_incidents_v1_show | Read read | 0 | Show Incidents V1 Official incident.io endpoint: GET /v1/incidents/{id} Get a single incident. |
incident-io.incident_io_ipallowlists_v1_show_ipallowlist | Read read | 0 | ShowIPAllowlist IPAllowlists V1 Official incident.io endpoint: GET /v1/ip_allowlists Show the IP allowlist for your organisation |
incident-io.incident_io_ipallowlists_v1_update_ipallowlist | Write write | 0 | UpdateIPAllowlist IPAllowlists V1 Official incident.io endpoint: PUT /v1/ip_allowlists Update the IP allowlist for your organisation |
incident-io.incident_io_maintenance_windows_v1_list | Read read | 0 | List MaintenanceWindows V1 Official incident.io endpoint: GET /v1/maintenance_windows List maintenance windows for your organisation. |
incident-io.incident_io_maintenance_windows_v1_create | Write write | 0 | Create MaintenanceWindows V1 Official incident.io endpoint: POST /v1/maintenance_windows Create a new maintenance window. |
incident-io.incident_io_maintenance_windows_v1_show | Read read | 0 | Show MaintenanceWindows V1 Official incident.io endpoint: GET /v1/maintenance_windows/{id} Show a particular maintenance window. |
incident-io.incident_io_maintenance_windows_v1_update | Write write | 0 | Update MaintenanceWindows V1 Official incident.io endpoint: PUT /v1/maintenance_windows/{id} Update an existing maintenance window. |
incident-io.incident_io_maintenance_windows_v1_delete | Write write | 0 | Delete MaintenanceWindows V1 Official incident.io endpoint: DELETE /v1/maintenance_windows/{id} Archives a maintenance window. Cannot archive active windows. |
incident-io.incident_io_utilities_v1_open_api | Read read | 0 | OpenAPI Utilities V1 Official incident.io endpoint: GET /v1/openapi.json Get the OpenAPI (v2) definition. **DEPRECATED**: Please use the OpenAPIV3 endpoint instead. The schema returned from this endpoint does not contain new options and end |
incident-io.incident_io_utilities_v1_open_apiv3 | Read read | 0 | OpenAPIV3 Utilities V1 Official incident.io endpoint: GET /v1/openapiV3.json Get the OpenAPI (v3) definition. |
incident-io.incident_io_postmortem_documents_v1_list | Read read | 0 | List PostmortemDocuments V1 Official incident.io endpoint: GET /v1/postmortem_documents List post-mortem documents for the organisation. Results can be filtered by incident and sorted by creation date. This endpoint returns document metadat |
incident-io.incident_io_postmortem_documents_v1_show | Read read | 0 | Show PostmortemDocuments V1 Official incident.io endpoint: GET /v1/postmortem_documents/{id} Get a single post-mortem document by ID. This returns the document's metadata. To retrieve the content of the post-mortem, use the ShowContent endp |
incident-io.incident_io_postmortem_documents_v1_update_status | Write write | 0 | UpdateStatus PostmortemDocuments V1 Official incident.io endpoint: PUT /v1/postmortem_documents/{id} Update the status of a post-mortem document. |
incident-io.incident_io_postmortem_documents_v1_show_content | Read read | 0 | ShowContent PostmortemDocuments V1 Official incident.io endpoint: GET /v1/postmortem_documents/{id}/content Fetch the content of a post-mortem document, rendered as markdown. The response contains the full document content as a single markd |
incident-io.incident_io_severities_v1_list | Read read | 0 | List Severities V1 Official incident.io endpoint: GET /v1/severities List all incident severities for an organisation. |
incident-io.incident_io_severities_v1_create | Write write | 0 | Create Severities V1 Official incident.io endpoint: POST /v1/severities Create a new severity |
incident-io.incident_io_severities_v1_show | Read read | 0 | Show Severities V1 Official incident.io endpoint: GET /v1/severities/{id} Get a single incident severity. |
incident-io.incident_io_severities_v1_update | Write write | 0 | Update Severities V1 Official incident.io endpoint: PUT /v1/severities/{id} Update an existing severity |
incident-io.incident_io_severities_v1_delete | Write write | 0 | Delete Severities V1 Official incident.io endpoint: DELETE /v1/severities/{id} Delete a severity |
incident-io.incident_io_status_pages_v1_list_response_incidents | Read read | 0 | ListResponseIncidents Status Pages V1 Official incident.io endpoint: GET /v1/status-pages/{id}/incidents/{incident_id}/response-incidents List the linked Response incidents for a status page incident. |
incident-io.incident_io_actions_v2_list | Read read | 0 | List Actions V2 Official incident.io endpoint: GET /v2/actions List all actions for an organisation. |
incident-io.incident_io_actions_v2_show | Read read | 0 | Show Actions V2 Official incident.io endpoint: GET /v2/actions/{id} Get a single incident action. |
incident-io.incident_io_alert_attributes_v2_list | Read read | 0 | List Alert Attributes V2 Official incident.io endpoint: GET /v2/alert_attributes List alert attributes. |
incident-io.incident_io_alert_attributes_v2_create | Write write | 0 | Create Alert Attributes V2 Official incident.io endpoint: POST /v2/alert_attributes Create a new alert attribute. |
incident-io.incident_io_alert_attributes_v2_show | Read read | 0 | Show Alert Attributes V2 Official incident.io endpoint: GET /v2/alert_attributes/{id} Show an alert attribute. |
incident-io.incident_io_alert_attributes_v2_update | Write write | 0 | Update Alert Attributes V2 Official incident.io endpoint: PUT /v2/alert_attributes/{id} Update an alert attribute. |
incident-io.incident_io_alert_attributes_v2_destroy | Write write | 0 | Destroy Alert Attributes V2 Official incident.io endpoint: DELETE /v2/alert_attributes/{id} Destroy an alert attribute. |
incident-io.incident_io_alert_events_v2_create_http | Write write | 0 | CreateHTTP Alert Events V2 Official incident.io endpoint: POST /v2/alert_events/http/{alert_source_config_id} Create an alert event using an HTTP source. |
incident-io.incident_io_alert_routes_v2_list | Read read | 0 | List Alert Routes V2 Official incident.io endpoint: GET /v2/alert_routes List all alert routes in your account. |
incident-io.incident_io_alert_routes_v2_create | Write write | 0 | Create Alert Routes V2 Official incident.io endpoint: POST /v2/alert_routes Create a new alert route in your account. |
incident-io.incident_io_alert_routes_v2_show | Read read | 0 | Show Alert Routes V2 Official incident.io endpoint: GET /v2/alert_routes/{id} Load details about a specific alert route in your account. |
incident-io.incident_io_alert_routes_v2_update | Write write | 0 | Update Alert Routes V2 Official incident.io endpoint: PUT /v2/alert_routes/{id} Update an existing alert route in your account. |
incident-io.incident_io_alert_routes_v2_delete | Write write | 0 | Delete Alert Routes V2 Official incident.io endpoint: DELETE /v2/alert_routes/{id} Delete an existing alert route in your account. |
incident-io.incident_io_alert_sources_v2_list | Read read | 0 | List Alert Sources V2 Official incident.io endpoint: GET /v2/alert_sources List all alert sources in your account. |
incident-io.incident_io_alert_sources_v2_create | Write write | 0 | Create Alert Sources V2 Official incident.io endpoint: POST /v2/alert_sources Create a new alert source in your account. |
incident-io.incident_io_alert_sources_v2_show | Read read | 0 | Show Alert Sources V2 Official incident.io endpoint: GET /v2/alert_sources/{id} Load details about a specific alert source in your account. |
incident-io.incident_io_alert_sources_v2_update | Write write | 0 | Update Alert Sources V2 Official incident.io endpoint: PUT /v2/alert_sources/{id} Update an existing alert source in your account. |
incident-io.incident_io_alert_sources_v2_delete | Write write | 0 | Delete Alert Sources V2 Official incident.io endpoint: DELETE /v2/alert_sources/{id} Delete an existing alert source in your account. |
incident-io.incident_io_alerts_v2_list | Read read | 0 | List Alerts V2 Official incident.io endpoint: GET /v2/alerts List all alerts for your account. This endpoint supports a number of filters, which can help find alerts matching certain criteria. These filters work similarly to the filters on |
incident-io.incident_io_alerts_v2_show | Read read | 0 | Show Alerts V2 Official incident.io endpoint: GET /v2/alerts/{id} Show a single alert for your account |
incident-io.incident_io_catalog_v2_list_entries | Read read | 0 | ListEntries Catalog V2 Official incident.io endpoint: GET /v2/catalog_entries List entries for a catalog type. |
incident-io.incident_io_catalog_v2_create_entry | Write write | 0 | CreateEntry Catalog V2 Official incident.io endpoint: POST /v2/catalog_entries Create an entry within the catalog. We support a maximum of 50,000 entries per type. If you call this API with a payload where the external_id and catalog_type_i |
incident-io.incident_io_catalog_v2_show_entry | Read read | 0 | ShowEntry Catalog V2 Official incident.io endpoint: GET /v2/catalog_entries/{id} Show a single catalog entry. |
incident-io.incident_io_catalog_v2_update_entry | Write write | 0 | UpdateEntry Catalog V2 Official incident.io endpoint: PUT /v2/catalog_entries/{id} Updates an existing catalog entry. |
incident-io.incident_io_catalog_v2_destroy_entry | Write write | 0 | DestroyEntry Catalog V2 Official incident.io endpoint: DELETE /v2/catalog_entries/{id} Archives a catalog entry. |
incident-io.incident_io_catalog_v2_list_resources | Read read | 0 | ListResources Catalog V2 Official incident.io endpoint: GET /v2/catalog_resources List available engine resources for the catalog. A resource represents a type of data that can be held within the catalog, so this endpoint can be used to see |
incident-io.incident_io_catalog_v2_list_types | Read read | 0 | ListTypes Catalog V2 Official incident.io endpoint: GET /v2/catalog_types List all catalog types for an organisation, including those synced from external resources. |
incident-io.incident_io_catalog_v2_create_type | Write write | 0 | CreateType Catalog V2 Official incident.io endpoint: POST /v2/catalog_types Create a catalog type. The schema must be updated using the UpdateTypeSchema endpoint. |
incident-io.incident_io_catalog_v2_show_type | Read read | 0 | ShowType Catalog V2 Official incident.io endpoint: GET /v2/catalog_types/{id} Show a single catalog type. |
incident-io.incident_io_catalog_v2_update_type | Write write | 0 | UpdateType Catalog V2 Official incident.io endpoint: PUT /v2/catalog_types/{id} Updates an existing catalog type. The schema must be updated using the UpdateTypeSchema endpoint. |
incident-io.incident_io_catalog_v2_destroy_type | Write write | 0 | DestroyType Catalog V2 Official incident.io endpoint: DELETE /v2/catalog_types/{id} Archives a catalog type and associated entries. |
incident-io.incident_io_catalog_v2_update_type_schema | Write write | 0 | UpdateTypeSchema Catalog V2 Official incident.io endpoint: POST /v2/catalog_types/{id}/actions/update_schema Update an existing catalog types schema, adding or removing attributes. Updating the schema is handled separately from creating and |
incident-io.incident_io_custom_fields_v2_list | Read read | 0 | List Custom Fields V2 Official incident.io endpoint: GET /v2/custom_fields List all custom fields for an organisation. |
incident-io.incident_io_custom_fields_v2_create | Write write | 0 | Create Custom Fields V2 Official incident.io endpoint: POST /v2/custom_fields Create a new custom field |
incident-io.incident_io_custom_fields_v2_show | Read read | 0 | Show Custom Fields V2 Official incident.io endpoint: GET /v2/custom_fields/{id} Get a single custom field. |
incident-io.incident_io_custom_fields_v2_update | Write write | 0 | Update Custom Fields V2 Official incident.io endpoint: PUT /v2/custom_fields/{id} Update the details of a custom field |
incident-io.incident_io_custom_fields_v2_delete | Write write | 0 | Delete Custom Fields V2 Official incident.io endpoint: DELETE /v2/custom_fields/{id} Delete a custom field |
incident-io.incident_io_escalations_v2_list_paths | Read read | 0 | ListPaths Escalations V2 Official incident.io endpoint: GET /v2/escalation_paths List all escalation paths in your account. An escalation path is a series of steps that describe how a page should be escalated, represented as a graph, suppor |
incident-io.incident_io_escalations_v2_create_path | Write write | 0 | CreatePath Escalations V2 Official incident.io endpoint: POST /v2/escalation_paths Create an escalation path. An escalation path is a series of steps that describe how a page should be escalated, represented as graph, supporting conditional |
incident-io.incident_io_escalations_v2_show_path | Read read | 0 | ShowPath Escalations V2 Official incident.io endpoint: GET /v2/escalation_paths/{id} Show an escalation path. We recommend you create escalation paths in the incident.io dashboard where our path builder makes it easy to use conditions and v |
incident-io.incident_io_escalations_v2_update_path | Write write | 0 | UpdatePath Escalations V2 Official incident.io endpoint: PUT /v2/escalation_paths/{id} Updates an escalation path. We recommend you create escalation paths in the incident.io dashboard where our path builder makes it easy to use conditions |
incident-io.incident_io_escalations_v2_destroy_path | Write write | 0 | DestroyPath Escalations V2 Official incident.io endpoint: DELETE /v2/escalation_paths/{id} Archives an escalation path. We recommend you create escalation paths in the incident.io dashboard where our path builder makes it easy to use condit |
incident-io.incident_io_escalations_v2_list | Read read | 0 | List Escalations V2 Official incident.io endpoint: GET /v2/escalations List all escalations for your account. This endpoint supports a number of filters, which can help find escalations matching certain criteria. Note that: - Filters may be |
incident-io.incident_io_escalations_v2_create | Write write | 0 | Create Escalations V2 Official incident.io endpoint: POST /v2/escalations Create an escalation. An escalation pages people, either according to an escalation path, or directly to specific users. You must provide either an escalation_path_id |
incident-io.incident_io_escalations_v2_show | Read read | 0 | Show Escalations V2 Official incident.io endpoint: GET /v2/escalations/{id} Show a specific escalation. |
incident-io.incident_io_follow_ups_v2_list | Read read | 0 | List Follow-ups V2 Official incident.io endpoint: GET /v2/follow_ups List all follow-ups for an organisation. |
incident-io.incident_io_follow_ups_v2_show | Read read | 0 | Show Follow-ups V2 Official incident.io endpoint: GET /v2/follow_ups/{id} Get a single incident follow-up. |
incident-io.incident_io_heartbeat_v2_ping_1 | Read read | 0 | Ping Heartbeat V2 Official incident.io endpoint: GET /v2/heartbeat/{alert_source_config_id}/ping Send a heartbeat ping for the specified alert source. Records a ping, indicating that the monitored job or service is healthy. The heartbeat mo |
incident-io.incident_io_heartbeat_v2_ping | Write write | 0 | Ping Heartbeat V2 Official incident.io endpoint: POST /v2/heartbeat/{alert_source_config_id}/ping Send a heartbeat ping for the specified alert source. Records a ping, indicating that the monitored job or service is healthy. The heartbeat m |
incident-io.incident_io_alerts_v2_list_incident_alerts | Read read | 0 | ListIncidentAlerts Alerts V2 Official incident.io endpoint: GET /v2/incident_alerts List the connections between incidents and alerts |
incident-io.incident_io_incident_roles_v2_list | Read read | 0 | List Incident Roles V2 Official incident.io endpoint: GET /v2/incident_roles List all incident roles for an organisation. |
incident-io.incident_io_incident_roles_v2_create | Write write | 0 | Create Incident Roles V2 Official incident.io endpoint: POST /v2/incident_roles Create a new incident role |
incident-io.incident_io_incident_roles_v2_show | Read read | 0 | Show Incident Roles V2 Official incident.io endpoint: GET /v2/incident_roles/{id} Get a single incident role. |
incident-io.incident_io_incident_roles_v2_update | Write write | 0 | Update Incident Roles V2 Official incident.io endpoint: PUT /v2/incident_roles/{id} Update an existing incident role |
incident-io.incident_io_incident_roles_v2_delete | Write write | 0 | Delete Incident Roles V2 Official incident.io endpoint: DELETE /v2/incident_roles/{id} Removes an existing role |
incident-io.incident_io_incident_timestamps_v2_list | Read read | 0 | List Incident Timestamps V2 Official incident.io endpoint: GET /v2/incident_timestamps List all incident timestamps for an organisation. |
incident-io.incident_io_incident_timestamps_v2_show | Read read | 0 | Show Incident Timestamps V2 Official incident.io endpoint: GET /v2/incident_timestamps/{id} Get a single incident timestamp. |
incident-io.incident_io_incident_updates_v2_list | Read read | 0 | List Incident Updates V2 Official incident.io endpoint: GET /v2/incident_updates List all incident updates for an organisation, or for a specific incident. |
incident-io.incident_io_incidents_v2_list | Read read | 0 | List Incidents V2 Official incident.io endpoint: GET /v2/incidents List all incidents for an organisation. This endpoint supports a number of filters, which can help find incidents matching certain criteria. Filters are provided as query pa |
incident-io.incident_io_incidents_v2_create | Write write | 0 | Create Incidents V2 Official incident.io endpoint: POST /v2/incidents Create a new incident. Note that if the incident mode is set to \"retrospective\" then the new incident will not be announced in Slack. |
incident-io.incident_io_incidents_v2_show | Read read | 0 | Show Incidents V2 Official incident.io endpoint: GET /v2/incidents/{id} Get a single incident. The ID supplied can be either the incident's full ID, or the numeric part of its reference. For example, to get INC-123, you could use either its |
incident-io.incident_io_incidents_v2_edit | Write write | 0 | Edit Incidents V2 Official incident.io endpoint: POST /v2/incidents/{id}/actions/edit Edit an existing incident. This endpoint allows you to edit the properties of an existing incident: e.g. set the severity or update custom fields. When us |
incident-io.incident_io_incidents_v2_import_postmortem_document | Write write | 0 | ImportPostmortemDocument Incidents V2 Official incident.io endpoint: POST /v2/incidents/{id}/actions/import_postmortem_document Import a postmortem document from markdown into an incident. The document content should be provided as GitHub-F |
incident-io.incident_io_schedules_v2_list_schedule_entries | Read read | 0 | ListScheduleEntries Schedules V2 Official incident.io endpoint: GET /v2/schedule_entries Get a list of schedule entries. The endpoint will return all entries that overlap with the given window, if one is provided. |
incident-io.incident_io_schedules_v2_create_override | Write write | 0 | CreateOverride Schedules V2 Official incident.io endpoint: POST /v2/schedule_overrides Create a new schedule override. |
incident-io.incident_io_schedules_v2_list | Read read | 0 | List Schedules V2 Official incident.io endpoint: GET /v2/schedules List configured schedules. |
incident-io.incident_io_schedules_v2_create | Write write | 0 | Create Schedules V2 Official incident.io endpoint: POST /v2/schedules Create a new schedule. |
incident-io.incident_io_schedules_v2_show | Read read | 0 | Show Schedules V2 Official incident.io endpoint: GET /v2/schedules/{id} Get a single schedule. |
incident-io.incident_io_schedules_v2_update | Write write | 0 | Update Schedules V2 Official incident.io endpoint: PUT /v2/schedules/{id} Update a schedule. |
incident-io.incident_io_schedules_v2_destroy | Write write | 0 | Destroy Schedules V2 Official incident.io endpoint: DELETE /v2/schedules/{id} Archives a single schedule. Will fail if the schedule has active replicas — remove all replicas before deleting. |
incident-io.incident_io_schedules_v2_list_schedule_replicas | Read read | 0 | ListScheduleReplicas Schedules V2 Official incident.io endpoint: GET /v2/schedules/{schedule_id}/replicas List all replicas for a schedule. |
incident-io.incident_io_schedules_v2_create_schedule_replica | Write write | 0 | CreateScheduleReplica Schedules V2 Official incident.io endpoint: POST /v2/schedules/{schedule_id}/replicas Create a new schedule replica. |
incident-io.incident_io_schedules_v2_show_schedule_replica | Read read | 0 | ShowScheduleReplica Schedules V2 Official incident.io endpoint: GET /v2/schedules/{schedule_id}/replicas/{id} Get a single schedule replica. |
incident-io.incident_io_schedules_v2_destroy_schedule_replica | Write write | 0 | DestroyScheduleReplica Schedules V2 Official incident.io endpoint: DELETE /v2/schedules/{schedule_id}/replicas/{id} Archives a single schedule replica, stopping incident.io from syncing on-call shifts to the external provider. As with disab |
incident-io.incident_io_status_pages_v2_create_status_page_incident_update | Write write | 0 | CreateStatusPageIncidentUpdate Status Pages V2 Official incident.io endpoint: POST /v2/status_page_incident_updates Post an update on a Status Page incident. This is the endpoint to use when resolving an incident - set incident_status to \"r |
incident-io.incident_io_status_pages_v2_list_status_page_incidents | Read read | 0 | ListStatusPageIncidents Status Pages V2 Official incident.io endpoint: GET /v2/status_page_incidents List status page incidents. This endpoint requires a valid API key but no specific scopes. |
incident-io.incident_io_status_pages_v2_create_status_page_incident | Write write | 0 | CreateStatusPageIncident Status Pages V2 Official incident.io endpoint: POST /v2/status_page_incidents Create a status page incident. This endpoint requires an API key with the \"Create status page incidents, status page maintenance windows, |
incident-io.incident_io_status_pages_v2_show_status_page_incident | Read read | 0 | ShowStatusPageIncident Status Pages V2 Official incident.io endpoint: GET /v2/status_page_incidents/{status_page_incident_id} Show a status page incident. This endpoint requires a valid API key but no specific scopes. |
incident-io.incident_io_status_pages_v2_update_status_page_incident | Write write | 0 | UpdateStatusPageIncident Status Pages V2 Official incident.io endpoint: PUT /v2/status_page_incidents/{status_page_incident_id} Update a status page incident. This endpoint requires an API key with the \"Create status page incidents, status |
incident-io.incident_io_status_pages_v2_create_status_page_maintenance_update | Write write | 0 | CreateStatusPageMaintenanceUpdate Status Pages V2 Official incident.io endpoint: POST /v2/status_page_maintenance_updates Post an update on a Status Page maintenance window. This is the endpoint to use when completing a maintenance window - |
incident-io.incident_io_status_pages_v2_list_status_page_maintenances | Read read | 0 | ListStatusPageMaintenances Status Pages V2 Official incident.io endpoint: GET /v2/status_page_maintenances List status page maintenances. This endpoint requires a valid API key but no specific scopes. |
incident-io.incident_io_status_pages_v2_create_status_page_maintenance | Write write | 0 | CreateStatusPageMaintenance Status Pages V2 Official incident.io endpoint: POST /v2/status_page_maintenances Schedule a Status Page maintenance window. This endpoint requires an API key with the \"Create status page incidents, status page ma |
incident-io.incident_io_status_pages_v2_show_status_page_maintenance | Read read | 0 | ShowStatusPageMaintenance Status Pages V2 Official incident.io endpoint: GET /v2/status_page_maintenances/{status_page_maintenance_id} Show a status page maintenance window. This endpoint requires a valid API key but no specific scopes. |
incident-io.incident_io_status_pages_v2_show_status_page_structure | Read read | 0 | ShowStatusPageStructure Status Pages V2 Official incident.io endpoint: GET /v2/status_page_structures/{status_page_id} Show the structure of a status page. This endpoint requires a valid API key but no specific scopes. Returns the component |
incident-io.incident_io_status_pages_v2_list_status_pages | Read read | 0 | ListStatusPages Status Pages V2 Official incident.io endpoint: GET /v2/status_pages List all status pages for your organisation. This endpoint requires a valid API key but no specific scopes. Use this to find status page IDs for use in othe |
incident-io.incident_io_telemetry_v2_update_data_source | Write write | 0 | UpdateDataSource Telemetry V2 Official incident.io endpoint: PUT /v2/telemetry/data_sources/{id} Update the credentials or configuration of a telemetry data source. Provide only the config block that matches your data source type (e.g. graf |
incident-io.incident_io_users_v2_list | Read read | 0 | List Users V2 Official incident.io endpoint: GET /v2/users List users in your account. |
incident-io.incident_io_users_v2_show | Read read | 0 | Show Users V2 Official incident.io endpoint: GET /v2/users/{id} Get a single user. |
incident-io.incident_io_users_v2_list_notification_methods | Read read | 0 | ListNotificationMethods Users V2 Official incident.io endpoint: GET /v2/users/{user_id}/notification_methods List notification methods for a user. Phone numbers are always partially redacted. |
incident-io.incident_io_users_v2_list_notification_rules | Read read | 0 | ListNotificationRules Users V2 Official incident.io endpoint: GET /v2/users/{user_id}/notification_rules List notification rules for a user. Rules define how and when a user is notified for on-call pages. Only includes high_urgency and low_ |
incident-io.incident_io_workflows_v2_list_workflows | Read read | 0 | ListWorkflows Workflows V2 Official incident.io endpoint: GET /v2/workflows List all workflows |
incident-io.incident_io_workflows_v2_create_workflow | Write write | 0 | CreateWorkflow Workflows V2 Official incident.io endpoint: POST /v2/workflows Create a new workflow |
incident-io.incident_io_workflows_v2_show_workflow | Read read | 0 | ShowWorkflow Workflows V2 Official incident.io endpoint: GET /v2/workflows/{id} Show a workflow by ID |
incident-io.incident_io_workflows_v2_update_workflow | Write write | 0 | UpdateWorkflow Workflows V2 Official incident.io endpoint: PUT /v2/workflows/{id} Updates a workflow |
incident-io.incident_io_workflows_v2_destroy_workflow | Write write | 0 | DestroyWorkflow Workflows V2 Official incident.io endpoint: DELETE /v2/workflows/{id} Archives a workflow |
incident-io.incident_io_catalog_v3_list_entries | Read read | 0 | ListEntries Catalog V3 Official incident.io endpoint: GET /v3/catalog_entries List entries for a catalog type. |
incident-io.incident_io_catalog_v3_create_entry | Write write | 0 | CreateEntry Catalog V3 Official incident.io endpoint: POST /v3/catalog_entries Create an entry within the catalog. We support a maximum of 50,000 entries per type. If you call this API with a payload where the external_id and catalog_type_i |
incident-io.incident_io_catalog_v3_bulk_update_entries | Write write | 0 | BulkUpdateEntries Catalog V3 Official incident.io endpoint: POST /v3/catalog_entries/actions/bulk_update Update multiple catalog entries in a single operation. You can update up to 250 entries at once. This operation is atomic - either all |
incident-io.incident_io_catalog_v3_show_entry | Read read | 0 | ShowEntry Catalog V3 Official incident.io endpoint: GET /v3/catalog_entries/{id} Show a single catalog entry. |
incident-io.incident_io_catalog_v3_update_entry | Write write | 0 | UpdateEntry Catalog V3 Official incident.io endpoint: PUT /v3/catalog_entries/{id} Updates an existing catalog entry. |
incident-io.incident_io_catalog_v3_destroy_entry | Write write | 0 | DestroyEntry Catalog V3 Official incident.io endpoint: DELETE /v3/catalog_entries/{id} Archives a catalog entry. |
incident-io.incident_io_catalog_v3_list_resources | Read read | 0 | ListResources Catalog V3 Official incident.io endpoint: GET /v3/catalog_resources List available engine resources for the catalog. A resource represents a type of data that can be held within the catalog, so this endpoint can be used to see |
incident-io.incident_io_catalog_v3_list_types | Read read | 0 | ListTypes Catalog V3 Official incident.io endpoint: GET /v3/catalog_types List all catalog types for an organisation, including those synced from external resources. |
incident-io.incident_io_catalog_v3_create_type | Write write | 0 | CreateType Catalog V3 Official incident.io endpoint: POST /v3/catalog_types Create a catalog type. The schema must be updated using the UpdateTypeSchema endpoint. |
incident-io.incident_io_catalog_v3_show_type | Read read | 0 | ShowType Catalog V3 Official incident.io endpoint: GET /v3/catalog_types/{id} Show a single catalog type. |
incident-io.incident_io_catalog_v3_update_type | Write write | 0 | UpdateType Catalog V3 Official incident.io endpoint: PUT /v3/catalog_types/{id} Updates an existing catalog type. The schema must be updated using the UpdateTypeSchema endpoint. |
incident-io.incident_io_catalog_v3_destroy_type | Write write | 0 | DestroyType Catalog V3 Official incident.io endpoint: DELETE /v3/catalog_types/{id} Archives a catalog type and associated entries. |
incident-io.incident_io_catalog_v3_update_type_schema | Write write | 0 | UpdateTypeSchema Catalog V3 Official incident.io endpoint: POST /v3/catalog_types/{id}/actions/update_schema Update an existing catalog types schema, adding or removing attributes. Updating the schema is handled separately from creating and |
incident-io.incident_io_teams_v3_list | Read read | 0 | List Teams V3 Official incident.io endpoint: GET /v3/teams List all teams in the organisation. |
incident-io.incident_io_teams_v3_show | Read read | 0 | Show Teams V3 Official incident.io endpoint: GET /v3/teams/{id} Get a single team. |