Incident Attachments V1

Create, list and delete incident attachments.

Incident Attachments allows you to connect resources from external systems into incidents. Examples include: PagerDuty incidents and GitHub pull requests.

List Incident Attachments V1

List all incident attachements for a given external resource or incident. You must provide either a specific incident ID or a specific external resource type and external ID.

Request
query Parameters
incident_id
string

Incident that this attachment is against

Example: incident_id=01G0J1EXE7AXZ2C93K61WBPYEH
external_id
string

ID of the resource in the external system

Example: external_id=123
resource_type
string

E.g. PagerDuty: the external system that holds the resource

Enum: "pager_duty_incident" "opsgenie_alert" "datadog_monitor_alert" "github_pull_request" "gitlab_merge_request" "sentry_issue" "jira_issue" "atlassian_statuspage_incident" "zendesk_ticket" "google_calendar_event" "scrubbed" "statuspage_incident" Examples:
resource_type=pager_duty_incident
Responses
200

OK response.

get/v1/incident_attachments
Request samples 
Response samples 
application/json
{
  • "incident_attachments": [
    ]
}
Create Incident Attachments V1
Attaches an external resource to an incident


Request 
Request Body schema: application/json
required
incident_id
required
string
ID of the incident to add an attachment to


 
required
object
 
Responses 
201
Created response.


post/v1/incident_attachments
Request samples 
application/json
{
  • "incident_id": "01FDAG4SAP5TYPT98WGR2N7W91",
  • "resource": {
    }
}
Response samples 
application/json
{
  • "incident_attachment": {
    }
}
Delete Incident Attachments V1
Unattaches an external resouce from an incident


Request 
path Parameters
id
required
string
Unique identifier of this incident membership


 
 Example:  01FCNDV6P870EA6S7TK1DSYD5H
Responses 
204
No Content response.


delete/v1/incident_attachments/{id}
Request samples 
➔ Next to Incident Memberships V1