Webhooks

Redrive (re-enqueue) failed webhook deliveries

Re-enqueues failed/exhausted deliveries of a webhook endpoint. OPS action: only the master of the owning organization (or the solo owner of an account with no org) can trigger it; a child sub-key → 403 FORBIDDEN.

Body: { delivery_id } re-enqueues one specific delivery, or { redrive_all_failed: true } re-enqueues ALL of the endpoint's failed/exhausted deliveries (cap 100).

Semantics: only failed/exhausted rows whose payload is still retained are re-enqueued → status→pending, attempts→0, next_retry_at→now(), last_error→null. The event_id/payload.id does NOT change (the SIEM keeps deduplicating). After the reset a best-effort immediate delivery is fired; the cron picks up whatever stays pending.

Zero-Retention: a success delivery already has its payload redacted ({redacted:true}) → nothing to resend → 409 PAYLOAD_REDACTED. A status that cannot be re-enqueued → 409 NOT_REDRIVABLE. Uniform anti-enumeration 404 (does not exist OR is not yours).

post/api/v1/webhooks/{id}/deliveries/redrive

Request

  • Base URL: https://legal.nexusquantum.legal
  • URL: https://legal.nexusquantum.legal/api/v1/webhooks/{id}/deliveries/redrive
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Request body

delivery_idstring uuid

Re-enqueues this specific delivery.

redrive_all_failedboolean

If true, re-enqueues ALL of the endpoint's failed/exhausted deliveries (cap 100).

Response

Deliveries re-enqueued.

redriveninteger required

Number of deliveries re-enqueued.

delivery_idsstring[] required

Ids of the re-enqueued deliveries.

skipped_redactedinteger

Batch mode only: rows skipped because their payload was already redacted (Zero-Retention).

cappedboolean

Batch mode only: true when the batch hit the cap (100) and more may remain.

requestIdstring

Changes

No recorded changes to this operation across all 1 revision of this API.