Send a delivery again
One more try at a delivery that has finished, `succeeded` or `failed`, sent now and once: the same event with the same body and `webhook-id` (a receiver that keeps the ids it has handled can tell it's the same one), signed with the webhook's secrets as every delivery is. For a receiver that was down or refused events: list the webhook's deliveries, fix the receiver, then send each `failed` one again (those still waiting when the webhook was turned off are `failed` too, `last_error` saying so). The answer is the delivery as this try left it: `succeeded`, with `delivered_at`, on a 2xx; otherwise its status stays as it was, with the receiver's answer in `last_status_code` and `last_error`, and the try never counts toward turning the webhook off. 409 `conflict` while the webhook is turned off (`POST …/webhooks/{webhook}/enable` first) or the delivery is still being tried (`pending`: its next attempt comes on its own). Needs `org.webhooks.edit`.
/v1/orgs/{org}/webhooks/{webhook}/deliveries/{delivery}/resendOne more try at a delivery that has finished, succeeded or failed, sent now and once: the same event with the same body and webhook-id (a receiver that keeps the ids it has handled can tell it's the same one), signed with the webhook's secrets as every delivery is. For a receiver that was down or refused events: list the webhook's deliveries, fix the receiver, then send each failed one again (those still waiting when the webhook was turned off are failed too, last_error saying so). The answer is the delivery as this try left it: succeeded, with delivered_at, on a 2xx; otherwise its status stays as it was, with the receiver's answer in last_status_code and last_error, and the try never counts toward turning the webhook off. 409 conflict while the webhook is turned off (POST …/webhooks/{webhook}/enable first) or the delivery is still being tried (pending: its next attempt comes on its own). Needs org.webhooks.edit.
Authorization
bearer An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.
In: header
Path Parameters
The org's id
^org_[0-9a-hjkmnp-tv-z]{26}$The webhook's id
^whk_[0-9a-hjkmnp-tv-z]{26}$The delivery's id, its webhook-id header
^msg_[0-9a-hjkmnp-tv-z]{26}$Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://api.synq.build/v1/orgs/org_01h455vb4pex5vsknk084sn02q/webhooks/whk_01h455vb4pex5vsknk084sn02q/deliveries/msg_01h455vb4pex5vsknk084sn02q/resend" \ -H "Authorization: Bearer $SYNQ_API_KEY"{ "id": "msg_01h455vb4pex5vsknk084sn02q", "event_type": "string", "status": "pending", "attempts": 0, "max_attempts": 6, "next_attempt_at": "2026-10-21T12:00:00.000Z", "last_status_code": 0, "last_error": "string", "delivered_at": "2026-10-21T12:00:00.000Z", "created_at": "2026-10-21T12:00:00.000Z"}A webhook's deliveries GET
Newest first, with their status, attempts and last answer. Needs `org.webhooks.view`.
Disconnect a Discord server DELETE
Takes the bot out of the server and stops every role the org's gates give there, from now on: whoever holds one keeps it, and nobody is checked there again. Connecting it again starts afresh. Needs `org.integrations.edit`. Recorded as `discord_server.disconnected`.