Documentation Index
Fetch the complete documentation index at: https://supahooks.ar27111994.dev/llms.txt
Use this file to discover all available pages before exploring further.
POST /replay/:webhookId/:itemId re-sends a previously captured webhook event to a destination URL you specify. The server validates the target against SSRF rules, strips masked and transport headers, injects replay-specific headers, and returns the target’s response code and body.
Authentication: Required when authKey is configured.
Path parameters
The webhook ID that owns the captured event.
The log entry ID to replay. If this does not resolve to a log ID but parses as a timestamp, the handler attempts a fallback lookup by timestamp within the specified webhook.
Query parameters
Destination URL to replay the event to. Subject to SSRF and DNS safety checks. Private networks, loopback addresses, and cloud metadata endpoints are blocked. See Error responses for the full blocked-range list.
Example request
Added headers
The server injects the following headers into every outbound replay request:| Header | Value |
|---|---|
X-Apify-Replay | true |
X-Original-Webhook-Id | The original webhook ID |
Idempotency-Key | A unique key for this replay attempt |
Stripped headers
Masked headers (e.g.Authorization, Cookie) and transport-managed headers (e.g. host, content-length) are removed before forwarding. The response body lists any headers that were stripped.
Success response
Error responses
Missing destination URL:Retry and timeout settings
You can tune replay behavior in Actor input:| Setting | Description |
|---|---|
replayMaxRetries | Number of delivery attempts before marking the replay as failed |
replayTimeoutMs | Per-attempt timeout in milliseconds. A dead downstream does not hang the actor beyond this value. |
504 Gateway Timeout with a machine-readable code field when one is available.