Internal Secret Incidents

Unlink a ticket from a secret incident, public incident or honeytoken

Changed on

Remove the link between a resource and a ticket previously created on an external platform (Jira, ServiceNow). The ticket itself is left untouched on the external platform: only the association with the resource is removed.

The resource_type query parameter selects the kind of resource resource_id designates: a secret incident, a public secret incident or a honeytoken.

ticket_id is the ticket's display ID on the external platform (for example PROJ-42 for Jira or INC0008111 for ServiceNow), as exposed by the id of the incident's destination_tickets entries.

If the same ticket is linked to the resource through several configurations, every one of those links is removed.

The scope needed depends on the resource: incidents:write for secret and public secret incidents, honeytokens:write for honeytokens. Unlinking from a public secret incident requires Public Monitoring to be active on the workspace, and unlinking from a honeytoken requires honeytokens to be enabled and, for a personal access token, a manager role.

delete/v1/incidents/secrets/{resource_id}/destination-tickets/{ticket_id}

Request

  • Base URL
    https://api.gitguardian.com
  • URL
    https://api.gitguardian.com/v1/incidents/secrets/{resource_id}/destination-tickets/{ticket_id}
  • Auth
    • HTTP bearer
    • or HTTP bearer

Path parameters

resource_idstring required

The id of the resource the ticket is linked to: an integer for a secret or public secret incident, a UUID for a honeytoken.

ticket_idstring required

The display ID of the ticket on the external platform, as exposed by the id of the incident's destination_tickets.

Query parameters

resource_type'secret-incidents' | 'public-secret-incidents' | 'honeytokens' required

The kind of resource resource_id designates.

Response

The ticket was unlinked successfully.

Changes

    • info

      the security scope incidents:write was added to the endpoint's security scheme api-key

    • info

      the security scope honeytokens:write was removed from the endpoint's security scheme api-key

    • info

      the security scope incidents:write was added to the endpoint's security scheme api-key

    • info

      the security scope honeytokens:write was removed from the endpoint's security scheme api-key