Skip to main content
The Webhook Debugger & Logger exposes a compact HTTP API for capturing incoming webhook traffic, querying and replaying stored events, streaming live activity, and probing the service’s health. All endpoints are available from the same base URL, whether you are running on Apify or self-hosting on localhost:8080.

​
Base URL

https://<run-id>.runs.apify.net
Replace <run-id> with the identifier of your Apify run. When self-hosting with Docker or Node.js directly, the server binds to port 8080 by default. You can override the port with the ACTOR_WEB_SERVER_PORT environment variable.

​
Endpoints

MethodPathDescription
GET/Built-in dashboard page (HTML or plain-text summary)
GET/infoRuntime metadata, active webhooks, and endpoint discovery
ANY/webhook/:idCapture incoming webhook traffic for any HTTP method
GET/logsQuery captured events with filtering and pagination
GET/logs/:logIdFetch a single captured event by ID
GET/logs/:logId/payloadRetrieve the raw payload for a captured event
GET/log-streamServer-Sent Events live feed of captured events
POST/replay/:webhookId/:itemIdReplay a captured event to a new destination URL
GET/system/metricsDataset-to-DuckDB sync service metrics
GET/healthLiveness probe
GET/readyReadiness probe

​
Runtime endpoint discovery

You can discover the full set of live endpoint URLs at runtime by calling GET /info. The response includes an endpoints map with fully-qualified URLs built from the running base URL, so you do not need to hard-code paths when integrating programmatically.

​
Authentication

Authentication is optional. When you supply an authKey in the Actor input, management endpoints and (optionally) webhook ingest require that key via a Bearer token header or ?key= query parameter. The /health and /ready probes are never protected. See Authentication for full details.