board-github

DELETE `/v1/board-github/links/{linkId}/items/{itemId}`

Remove an item from the GitHub Project, permanently.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X DELETE https://api.zinndigital.com/v1/board-github/links/{linkId}/items/{itemId}?confirm=<confirm> \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

**There is no undo, on either side.** For a draft item GitHub destroys the content outright; for an issue or a pull request the item leaves the project and the issue itself survives. A customer cannot be expected to know which of those they are about to do, so the screen says it and this endpoint refuses without an explicit confirmation. `confirm` must equal the item's own GitHub node id (`item_node_id`), not a boolean and not the word "delete". A boolean confirms *that you meant to delete something*; the node id confirms *which one*, so a stale tab, a re-sorted board or a double submit that lands on a neighbouring row is refused rather than granted. Archiving is the reversible alternative and is usually what a person clearing a Done column actually wants — see the `archive` sub-resource.

Parameters

Name	Type	Required	What it is
`linkId (path)`	`string`	Yes	The GitHub Projects connection.
`itemId (path)`	`string`	Yes	The item, by OUR id — not GitHub's node id, which is not a path-safe value.
`confirm (query)`	`string`	Yes	The item's own `item_node_id`. A query parameter rather than a request body because a `DELETE` body is dropped by enough proxies that a confirmation carried in one silently beco…

Errors this endpoint can return

401 · 403 · 404 · 422

DELETE /v1/board-github/links/{linkId}/items/{itemId}