board-github
DELETE /v1/board-github/links/{linkId}/items/{itemId}
Remove an item from the GitHub Project, permanently.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X DELETE https://api.zinndigital.com/v1/board-github/links/{linkId}/items/{itemId}?confirm=<confirm> \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
**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.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
linkId (path) | string | 是 | The GitHub Projects connection. |
itemId (path) | string | 是 | The item, by OUR id — not GitHub's node id, which is not a path-safe value. |
confirm (query) | string | 是 | 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… |
此端点可能返回的错误
401 · 403 · 404 · 422