> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # 删除 Webhook 目标 API > 永久删除一个 Didit Webhook 目标，连同其签名密钥和投递日志一并删除。Webhook 操作按次计费，无需签订任何合同。 删除 Webhook 目标 API 提示词 将提示词复制到剪贴板 \

\`Delete a Didit webhook destination through the Management API.

Endpoint:
DELETE https://verification.didit.me/v3/webhook/destinations/{destination_uuid}/

Authentication:
Use the x-api-key header with my Didit API key.

Goal:
\- Delete a destination so Didit stops pushing webhooks to its URL. Use this when retiring an integration, rotating to a new URL, or cleaning up test destinations.

Path parameter:
\- destination_uuid — the destination UUID from GET /v3/webhook/destinations/.

Important semantics:
\- After this call, no new webhook is sent to this destination's URL. Other destinations subscribed to the same events keep receiving deliveries.
\- The destination, its signing secret and its entire delivery log are deleted permanently and cannot be recovered; its deliveries, delivery detail and resend routes answer 404.
\- The destination disappears from GET /v3/webhook/destinations/ and subsequent GET /v3/webhook/destinations/{destination_uuid}/ calls return 404.
\- Didit also updates the application's legacy webhook_url: it becomes the URL of the oldest remaining enabled destination, or is cleared when no enabled destination is left, so other tooling sees "no webhook configured".
\- Returns 204 No Content with an empty body on success.
\- Idempotent in effect: calling DELETE again on the same UUID returns 404.

Workflow when rotating endpoints:
1\. POST /v3/webhook/destinations/ to create the new destination and capture its secret_shared_key.
2\. Verify the new endpoint is receiving and validating webhooks correctly.
3\. DELETE the old destination.

Example call:
curl -X DELETE "https://verification.didit.me/v3/webhook/destinations/{destination_uuid}/" \
-H "x-api-key: YOUR_API_KEY"

Failure modes:
\- 401 — missing or malformed x-api-key.
\- 403 — canonical { "detail": "You do not have permission to perform this action." } envelope.
\- 404 — destination not found in this application (or already deleted).

Side effects:
\- The destination, its signing secret and its delivery log are deleted permanently. This cannot be undone.
\- No new webhook is sent to its URL.

For the full integration shape, see /integration/integration-prompt.`

\
粘贴到 > [!WARNING] > > 删除目标是永久性操作。 > 该目标、其签名密钥及其完整的投递日志都会被删除，且无法恢复。 ## OpenAPI ````yaml zh/openapi-25.json DELETE /v3/webhook/destinations/{destination_uuid}/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: 身份证件验证 API。使用 x-api-key 请求头进行身份验证。 servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/webhook/destinations/{destination_uuid}/: delete: tags: - Webhook summary: 删除 Webhook 目标 description: >- 永久删除一个 Webhook 目标、其签名密钥及其整个投递日志。此操作无法撤销。系统不会向该目标的 URL 发送新的 Webhook；订阅相同事件的其他目标将继续接收这些事件。删除后，该目标不再出现在 `GET /v3/webhook/destinations/` 中，且 `/v3/webhook/destinations/{destination_uuid}/` 下的所有路由（包括其投递记录、某次投递的详情及其重新发送）均返回 404。该应用的旧版 `webhook_url` 将设置为保留的最早启用的目标的 URL，若无启用的目标保留则清空。再次调用 DELETE 返回 404。 operationId: delete_webhook_destination parameters: - name: destination_uuid in: path required: true description: 要删除的 Webhook 目标的 UUID。 schema: type: string format: uuid example: 11111111-2222-3333-4444-555555555555 responses: '204': description: 目标、签名密钥和投递日志已永久删除。无响应体。 '403': description: API 密钥缺失、格式错误、已过期或作用域属于其他应用。密钥缺失返回 `403`；密钥错误、已撤销或已过期返回 `401`。 content: application/json: examples: Forbidden: value: detail: You do not have permission to perform this action. '404': description: 应用不存在具有此 UUID 的目标（已删除或从未存在）。 content: application/json: examples: Not found: value: detail: Webhook destination not found. '429': description: 超出速率限制；请退避并重试。 content: application/json: examples: Throttled: value: detail: Request was throttled. Expected available in 30 seconds. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X DELETE 'https://verification.didit.me/v3/webhook/destinations/11111111-2222-3333-4444-555555555555/' \ -H 'x-api-key: YOUR_API_KEY' - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY. client = Didit() client.webhooks.destinations.delete( "11111111-2222-3333-4444-555555555555", ) - lang: javascript label: Node.js source: >- import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY. const didit = new Didit(); await didit.webhooks.destinations.delete("11111111-2222-3333-4444-555555555555"); - lang: go label: Go source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\nif err := client.Webhooks.Destinations.Delete(ctx, \"11111111-2222-3333-4444-555555555555\"); err != nil {\n\tlog.Fatal(err)\n}" - lang: java label: Java source: >- import me.didit.Didit; // Reads DIDIT_API_KEY. Didit client = new Didit(); client.webhooks().destinations().delete("11111111-2222-3333-4444-555555555555"); - lang: php label: PHP source: >- webhooks->destinations->delete('11111111-2222-3333-4444-555555555555'); - lang: ruby label: Ruby source: >- require "didit" # Reads DIDIT_API_KEY. didit = Didit::Client.new didit.webhooks.destinations.delete("11111111-2222-3333-4444-555555555555") - lang: csharp label: .NET source: >- using System; using Didit; // Reads DIDIT_API_KEY. using var client = new DiditClient(); await client.Webhooks.Destinations.DeleteAsync("11111111-2222-3333-4444-555555555555"); components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- 您的应用 API 密钥，可在 Business Console 的“开发者 -> API 密钥”中获取。主密钥拥有完整访问权限。指定名称的密钥可设置作用域：针对每个资源设为无权限、只读或读写，限定于特定工作流或已通过的会话、限定于 IP 地址列表，以及设置到期日期。401 表示密钥错误、已撤销或已过期；403 表示未发送密钥、密钥无权访问该资源或操作，或请求来自其 IP 列表之外的地址；在会话路由上返回 404 表示该会话不在该密钥允许的工作流或状态范围内。没有媒体访问权限的密钥获取到的图片、视频和 PDF URL 将为 null；没有会话写入权限的密钥获取到的会话链接和 token 将为 null。请参阅 https://docs.didit.me/console/api-keys。 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.