Skip to main content
POST
Replay a webhook delivery
Request an idempotent replay of a Praxa webhook delivery after correcting the destination failure.
Availability: Partner preview. Required scopes: runs:write, runs:read.

Authenticate safely

Create a disposable personal workspace API key with exactly runs:write and runs:read. Send it as Authorization: Bearer $PRAXA_API_KEY. A Gateway OAuth token, Supabase JWT, provider credential, or organization memory key is not interchangeable with this key. The hosted playground sends the credential from your browser session to the documented API through the configured playground proxy. Use test data, never share the key, and revoke it when the check ends.

Request fields

string
required
deliveryId path parameter.

Runnable request examples

What success means

A 202 response returns the created or idempotently reused replay delivery; it does not prove destination acceptance.

Successful response

202 — The created or idempotently reused replay delivery.
v1
required
apiVersion response field.
string
required
id response field.
string
required
endpoint_id response field.
run.accepted | run.started | run.progress | approval.required | approval.resolved | run.completed | run.failed | run.cancelled
required
event_type response field.
string
run_id response field.
pending | delivering | succeeded | retrying | dead_letter
required
status response field.
integer
required
attempt_count response field.
integer
response_status response field.
string
next_attempt_at response field.
string
delivered_at response field.
string
required
createdAt response field.
string
required
updatedAt response field.

Handle failures

Example problem

Verify the result

  1. Fix and health-check the destination before replaying.
  2. Follow delivery readback to its final status.
  3. Repeat the same replay request and require one logical replay.

Retry, cleanup, and production use

  • Treat 401, 403, and 409 as authority or state signals, not generic retry prompts.
  • For 429 or retryable 5xx responses, follow server retry guidance and keep a bounded attempt budget.
  • Move the request into a trusted application backend before production; never ship the Praxa key in browser or mobile code.
  • Revoke the disposable key, disable test webhooks, and erase disposable candidate data after validation.
Continue with API authentication, the failure and retry guide, and the end-to-end coverage matrix.
Last modified on August 14, 2026