--- title: "Create an incident integration metadata" method: POST path: "/api/v2/incidents/{incident_id}/relationships/integrations" tags: ["Incidents"] --- # Create an incident integration metadata `POST /api/v2/incidents/{incident_id}/relationships/integrations` ## Request - Base URL: `https://api.datadoghq.com` - URL: `https://api.datadoghq.com/api/v2/incidents/{incident_id}/relationships/integrations` - Auth: one of: - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY` - OAuth 2 - Authorization code: `/oauth2/v1/authorize` - Token URL: `/oauth2/v1/token` scopes: `incident_write` Create an incident integration metadata. ## Path parameters - `incident_id` string, required ## Request body - IncidentIntegrationMetadataCreateRequest: Create request for an incident integration metadata. - `data` IncidentIntegrationMetadataCreateData, required: Incident integration metadata data for a create request. - `attributes` IncidentIntegrationMetadataAttributes, required: Incident integration metadata's attributes for a create request. - `created` string, date-time: Timestamp when the incident todo was created. - `incident_id` string: UUID of the incident this integration metadata is connected to. - `integration_type` integer, required: A number indicating the type of integration this metadata is for. 1 indicates Slack; 7 indicates Microsoft Teams; 8 indicates Jira. - `metadata` union, required: Incident integration metadata's metadata attribute. - SlackIntegrationMetadata: Incident integration metadata for the Slack integration. - `channels` SlackIntegrationMetadataChannelItem[], required: Array of Slack channels in this integration metadata. - `channel_id` string, required: Slack channel ID. - `channel_name` string, required: Name of the Slack channel. - `redirect_url` string, required: URL redirecting to the Slack channel. - `team_id` string: Slack team ID. - JiraIntegrationMetadata: Incident integration metadata for the Jira integration. - `issues` JiraIntegrationMetadataIssuesItem[], required: Array of Jira issues in this integration metadata. - `account` string, required: URL of issue's Jira account. - `issue_key` string: Jira issue's issue key. - `issuetype_id` string: Jira issue's issue type. - `project_key` string, required: Jira issue's project keys. - `redirect_url` string: URL redirecting to the Jira issue. - MSTeamsIntegrationMetadata: Incident integration metadata for the Microsoft Teams integration. - `teams` MSTeamsIntegrationMetadataTeamsItem[], required: Array of Microsoft Teams in this integration metadata. - `ms_channel_id` string, required: Microsoft Teams channel ID. - `ms_channel_name` string, required: Microsoft Teams channel name. - `ms_tenant_id` string, required: Microsoft Teams tenant ID. - `redirect_url` string, required: URL redirecting to the Microsoft Teams channel. - `modified` string, date-time: Timestamp when the incident todo was last modified. - `status` integer: A number indicating the status of this integration metadata. 0 indicates unknown; 1 indicates pending; 2 indicates complete; 3 indicates manually created; 4 indicates manually updated; 5 indicates failed. - `type` 'incident_integrations', required: Integration metadata resource type. ## Response `201` CREATED - IncidentIntegrationMetadataResponse: Response with an incident integration metadata. - `data` IncidentIntegrationMetadataResponseData, required: Incident integration metadata from a response. - `attributes` IncidentIntegrationMetadataAttributes: Incident integration metadata's attributes for a create request. - `created` string, date-time: Timestamp when the incident todo was created. - `incident_id` string: UUID of the incident this integration metadata is connected to. - `integration_type` integer, required: A number indicating the type of integration this metadata is for. 1 indicates Slack; 7 indicates Microsoft Teams; 8 indicates Jira. - `metadata` union, required: Incident integration metadata's metadata attribute. - SlackIntegrationMetadata: Incident integration metadata for the Slack integration. - `channels` SlackIntegrationMetadataChannelItem[], required: Array of Slack channels in this integration metadata. - `channel_id` string, required: Slack channel ID. - `channel_name` string, required: Name of the Slack channel. - `redirect_url` string, required: URL redirecting to the Slack channel. - `team_id` string: Slack team ID. - JiraIntegrationMetadata: Incident integration metadata for the Jira integration. - `issues` JiraIntegrationMetadataIssuesItem[], required: Array of Jira issues in this integration metadata. - `account` string, required: URL of issue's Jira account. - `issue_key` string: Jira issue's issue key. - `issuetype_id` string: Jira issue's issue type. - `project_key` string, required: Jira issue's project keys. - `redirect_url` string: URL redirecting to the Jira issue. - MSTeamsIntegrationMetadata: Incident integration metadata for the Microsoft Teams integration. - `teams` MSTeamsIntegrationMetadataTeamsItem[], required: Array of Microsoft Teams in this integration metadata. - `ms_channel_id` string, required: Microsoft Teams channel ID. - `ms_channel_name` string, required: Microsoft Teams channel name. - `ms_tenant_id` string, required: Microsoft Teams tenant ID. - `redirect_url` string, required: URL redirecting to the Microsoft Teams channel. - `modified` string, date-time: Timestamp when the incident todo was last modified. - `status` integer: A number indicating the status of this integration metadata. 0 indicates unknown; 1 indicates pending; 2 indicates complete; 3 indicates manually created; 4 indicates manually updated; 5 indicates failed. - `id` string, required: The incident integration metadata's ID. - `relationships` IncidentIntegrationRelationships: The incident's integration relationships from a response. - `created_by_user` RelationshipToUser: Relationship to user. - `data` RelationshipToUserData, required: Relationship to user object. - `id` string, required: A unique identifier that represents the user. - `type` 'users', required: Users resource type. - `last_modified_by_user` RelationshipToUser: Relationship to user. - `data` RelationshipToUserData, required: Relationship to user object. - `id` string, required: A unique identifier that represents the user. - `type` 'users', required: Users resource type. - `type` 'incident_integrations', required: Integration metadata resource type. - `included` IncidentIntegrationMetadataResponseIncludedItem[]: Included related resources that the user requested. - `attributes` UserAttributes: Attributes of user object returned by the API. - `created_at` string, date-time: The ISO 8601 timestamp of when the user account was created. - `disabled` boolean: Whether the user account is deactivated. Disabled users cannot log in. - `email` string: The email address of the user, used for login and notifications. - `handle` string: The unique handle (username) of the user, typically matching their email prefix. - `icon` string: URL of the user's profile icon, typically a Gravatar URL derived from the email address. - `last_login_time` string, date-time, nullable: The ISO 8601 timestamp of the user's most recent login, or null if the user has never logged in. - `mfa_enabled` boolean: Whether multi-factor authentication (MFA) is enabled for the user's account. - `modified_at` string, date-time: The ISO 8601 timestamp of when the user account was last modified. - `name` string, nullable: The full display name of the user as shown in the Datadog UI. - `service_account` boolean: Whether this is a service account rather than a human user. Service accounts are used for programmatic API access. - `status` string: The current status of the user account (for example, `Active`, `Pending`, or `Disabled`). - `title` string, nullable: The job title of the user (for example, "Senior Engineer" or "Product Manager"). - `uuid` string: The globally unique identifier (UUID) of the user. - `verified` boolean: Whether the user's email address has been verified. - `id` string: ID of the user. - `relationships` UserResponseRelationships: Relationships of the user object returned by the API. - `org` RelationshipToOrganization: Relationship to an organization. - `data` RelationshipToOrganizationData, required: Relationship to organization object. - `id` string, required: ID of the organization. - `type` 'orgs', required: Organizations resource type. - `other_orgs` RelationshipToOrganizations: Relationship to organizations. - `data` RelationshipToOrganizationData[], required: Relationships to organization objects. - `id` string, required: ID of the organization. - `type` 'orgs', required: Organizations resource type. - `other_users` RelationshipToUsers: Relationship to users. - `data` RelationshipToUserData[], required: Relationships to user objects. - `id` string, required: A unique identifier that represents the user. - `type` 'users', required: Users resource type. - `roles` RelationshipToRoles: Relationship to roles. - `data` RelationshipToRoleData[]: An array containing type and the unique identifier of a role. - `id` string: The unique identifier of the role. - `type` 'roles': Roles type. - `type` 'users': Users resource type. ## Other responses - `400`: Bad Request - `401`: Unauthorized - `403`: Forbidden - `404`: Not Found - `429`: Too many requests --- [API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/da68bf029e4c?raw)