API Reference · Control-plane API

Replay Webhook Deliveries

Requeue eligible failed or dead-letter deliveries for one webhook endpoint within a bounded time window.

Endpoint contract

POST/org/webhooks/{endpoint_id}/replay

200 OK

Use the exact method and path shown above. Paths are relative to the API base URL.

Authentication, permission, and scope

Control	Required contract
Authentication	Bearer access token.
Permission or scope	`webhooks.manage` capability and `webhooks:write` scope.
Resource scope	The endpoint and selected deliveries must belong to the caller’s organization and active project context.

Request fields

Field	Type	Contract
`endpoint_id`	integer path parameter	Target webhook endpoint.
`since_minutes`	integer	1–10080; defaults to 60.
`statuses`	string[]	Defaults to `failed` and `dead_letter`.
`limit`	integer	1–1000; defaults to 100.

Code examples

import os
from memorysync import ControlPlaneClient

client = ControlPlaneClient(
    base_url="https://api.memorysync.io",
    access_token=os.environ["MEMORYSYNC_ACCESS_TOKEN"],
)

result = client.replay_webhook_deliveries(
    51,
    since_minutes=240,
    statuses=["failed", "dead_letter"],
    limit=100,
    project_id=os.environ["MEMORYSYNC_PROJECT_ID"],
)

Response shape

response.json

{"endpoint_id":51,"eligible":12,"replayed":10,"skipped":2,"delivery_ids":[8801,8802,8803]}

Deliveries at their maximum attempt count are skipped.
A replayed count confirms requeueing, not successful downstream receipt.

Status outcomes

HTTP outcomes

2xx

Request completed

Read the operation-specific response and persist only fields needed by the task.

400 / 422

Correct the request

Fix invalid path, query, or body fields before trying again.

401 / 403

Access denied

Refresh authentication or verify the required organization permission and scope.

404

Unavailable in scope

Treat the resource as unavailable without revealing whether it exists elsewhere.

429 / 5xx

Keep the action recoverable

Use returned retry metadata when present and reconcile uncertain mutations before repeating them.

Production handling

01
Authorize
APP
Confirm the signed-in principal may perform this product action.
02
Validate
INPUT
Validate identifiers and body fields before sending the request.
03
Call
SDK
Use the named ControlPlaneClient method or equivalent HTTPS request from a trusted application context.
04
Inspect
RESULT
Compare eligible, replayed, and skipped before reporting completion.
05
Reconcile
SAFE
Monitor the returned delivery IDs and avoid overlapping replay windows from concurrent operators.

Security notes

Required

Keep organization controls inside trusted boundaries.

Confirm the downstream incident is resolved before replay.
Use narrow windows and bounded limits.
Expect receivers to handle duplicate event delivery safely.

Avoid

Do not weaken the route contract in client code.

Do not expose bearer or refresh tokens in URLs, logs, or public clients.
Do not accept organization, member, project, or resource IDs without application authorization.
Do not treat returned data as trusted HTML, prompt instructions, or proof of application authorization.

Webhook Deliveries

Find failed delivery IDs and status.

Test Webhook

Verify the endpoint before bulk replay.

Authentication

Compare bearer-authenticated control-plane clients with the memory API-key client.

API Overview

Choose the SDK client and authentication contract for the operation.

Was this page helpful?

← Previous