---
title: "Unlink a Ticket from Findings"
method: POST
path: "/api/notifications/deployments/{deploymentId}/ticketing/v2/{ticketingInstanceId}/tickets/unlink"
tags: ["ExternalTicketingService"]
---

# Unlink a Ticket from Findings

`POST /api/notifications/deployments/{deploymentId}/ticketing/v2/{ticketingInstanceId}/tickets/unlink`

## Request

- The document declares no server URL.
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
- TypeScript: <https://skmtc.dev/semgrep/apis/semgrep-web-app/docs/api/notifications/deployments/:deploymentId/ticketing/v2/:ticketingInstanceId/tickets/unlink/post.ts> (a function with typed inputs; its response is checked against the schema)

Remove the ticket association from one or more Semgrep findings by providing a list of finding IDs. This does not delete the ticket in your issue tracker — it only removes the association in Semgrep.

## Path parameters

- `deploymentId` integer, required: The unique numerical identifier of the deployment associated with the finding. Can be found via the [Deployments Service](#tag/DeploymentsService) or in your Settings in the web UI.
- `ticketingInstanceId` integer, required: The unique numerical identifier of the ticketing instance. Can be found via the [Get External Ticketing Instances](#tag/ExternalTicketingService/operation/ExternalTicketingService_GetNangoTicketingInstances) endpoint.

## Request body

- ProtosTicketingV2UnlinkTicketRequest: UnlinkTicket
  - `issueIds` integer[]: An array of Semgrep finding IDs to unlink tickets from.

## Response `200`

OK

- ProtosTicketingV2UnlinkTicketResponse
  - `unlinkedIssueIds` integer[]

---

[API](https://skmtc.dev/semgrep/apis/semgrep-web-app.md) - [All operations](https://skmtc.dev/semgrep/apis/semgrep-web-app/llms.txt) - [OpenAPI document](https://skmtc.dev/semgrep/apis/semgrep-web-app/revisions/6483eeecd582?raw)