agency-board
POST /v1/agency/boards/{boardId}/webhook-deliveries/{deliveryId}/replay
Send the same payload again.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/agency/boards/{boardId}/webhook-deliveries/{deliveryId}/replay \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Re-sends the STORED bytes with a fresh timestamp and a fresh signature over those same bytes. Nothing is re-serialised — a different byte string would produce a signature the receiver cannot verify, which fails as "your signatures are wrong" on their side and is unfalsifiable from ours.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
boardId (path) | Uuid | 是 | Project board ID (UUIDv7). |
deliveryId (path) | Uuid | 是 | Webhook delivery ID (UUIDv7). |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
id | Uuid | 是 | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
subscription_id | Uuid | 是 | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
event | string | 是 | — |
delivery_key | string | 是 | Sent as X-Zinn-Delivery, so the receiver can dedupe too. |
payload | object | 否 | The body exactly as it was signed and sent. |
status | BoardWebhookDeliveryStatus | 是 | — |
attempts | integer | 是 | — |
response_status | integer | 否 | — |
response_snippet | string | 否 | The first 500 bytes your endpoint answered with. When it answered but sent no body, the status we observed; when we could not reach it, or the fault was ours, authored copy saying… |
next_attempt_at | string | 否 | — |
delivered_at | string | 否 | — |
replay_of_id | Uuid | 否 | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
created_at | string | 是 | — |
此端点可能返回的错误
401 · 403 · 404