Replay a webhook delivery
curl --request POST \
--url https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"apiVersion": "v1",
"id": "018f0000-0000-7000-8000-000000000001",
"endpoint_id": "endpoint-demo-0001",
"event_type": "run.accepted",
"status": "pending",
"attempt_count": 0,
"createdAt": "2026-08-13T12:00:00.000Z",
"updatedAt": "2026-08-13T12:00:00.000Z"
}
Webhooks
Replay a webhook delivery
Request an idempotent replay of a Praxa webhook delivery after correcting the destination failure.
POST
/
v1
/
webhook-deliveries
/
{deliveryId}
/
replay
Replay a webhook delivery
curl --request POST \
--url https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.praxa.io/v1/webhook-deliveries/{deliveryId}/replay"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"apiVersion": "v1",
"id": "018f0000-0000-7000-8000-000000000001",
"endpoint_id": "endpoint-demo-0001",
"event_type": "run.accepted",
"status": "pending",
"attempt_count": 0,
"createdAt": "2026-08-13T12:00:00.000Z",
"updatedAt": "2026-08-13T12:00:00.000Z"
}
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 exactlyruns: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
curl --fail-with-body -X POST 'https://api.praxa.io/v1/webhook-deliveries/delivery-demo-0001/replay' \
-H "Authorization: Bearer $PRAXA_API_KEY" \
-H "Content-Type: application/json" \
--data '{}'
const response = await fetch("https://api.praxa.io/v1/webhook-deliveries/delivery-demo-0001/replay", {
"method": "POST",
"headers": {
"Authorization": `Bearer ${process.env.PRAXA_API_KEY}`,
"Content-Type": "application/json"
},
"body": JSON.stringify({})
});
const text = await response.text();
if (!response.ok) throw new Error(`${response.status}: ${text}`);
console.log(text ? JSON.parse(text) : { status: response.status });
import json
import os
from urllib import error, request
payload = json.dumps({}).encode()
req = request.Request(
"https://api.praxa.io/v1/webhook-deliveries/delivery-demo-0001/replay",
method="POST",
headers={
"Authorization": f"Bearer {os.environ['PRAXA_API_KEY']}",
"Content-Type": "application/json"
},
data=payload,
)
try:
with request.urlopen(req, timeout=30) as response:
text = response.read().decode()
print(json.loads(text) if text else {"status": response.status})
except error.HTTPError as exc:
raise RuntimeError(f"{exc.code}: {exc.read().decode()}") from exc
What success means
A202 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.
{
"apiVersion": "v1",
"id": "018f0000-0000-7000-8000-000000000001",
"endpoint_id": "endpoint-demo-0001",
"event_type": "run.accepted",
"status": "pending",
"attempt_count": 0,
"createdAt": "2026-08-13T12:00:00.000Z",
"updatedAt": "2026-08-13T12:00:00.000Z"
}
Handle failures
| Response | Meaning | Safe action |
|---|---|---|
400 invalid_request | The method, path, headers, query, or body failed strict validation. | Correct the request; do not retry unchanged input. |
401 authentication_failed | The bearer key is missing, malformed, expired, or revoked. | Stop and replace the key through the authenticated console. |
403 authorization_failed | The authenticated key lacks scope or tenant authority. | Request only the missing least-privilege scope; never substitute another tenant ID. |
429 rate_limited | The principal exceeded a bounded rate. | Honor retryAfterMs or Retry-After, add jitter, and cap attempts. |
retryable 5xx | The server could not confirm a final response. | Reconcile reads or replay the exact keyed mutation before creating new work. |
Example problem
{
"type": "https://docs.praxa.io/problems/authorization-failed",
"title": "Authorization failed",
"status": 403,
"code": "authorization_failed",
"detail": "The API key does not grant the required scope.",
"retryable": false
}
Verify the result
- Fix and health-check the destination before replaying.
- Follow delivery readback to its final status.
- Repeat the same replay request and require one logical replay.
Retry, cleanup, and production use
- Treat
401,403, and409as authority or state signals, not generic retry prompts. - For
429or 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.
Last modified on August 14, 2026