API Reference
Instant webhook debugging in real-time. Access our REST API to programmatically manage channels, retrieve logs, and configure routing rules.
Core API Resources
Interact with WebhookLab using standard HTTP methods. All requests require Bearer authentication via the Authorization header.
Channel Management
GET /api/v1/channels - List all active listening URLs
POST /api/v1/channels - Provision a new custom subdomain
DELETE /api/v1/channels/{id} - Terminate and purge channel data
Log Retrieval
GET /api/v1/logs?channel_id={id}&limit=50 - Fetch recent payloads
GET /api/v1/logs/{request_id} - Retrieve raw headers, body, and response metadata
POST /api/v1/logs/{request_id}/replay - Trigger an instant replay to your origin
Rule Configuration
PUT /api/v1/rules/{id} - Update regex matching and forwarding logic
GET /api/v1/rules - Audit active transformation rules
DELETE /api/v1/rules/{id} - Disable payload filtering or header injection
Request & Response Patterns
See how to authenticate, structure payloads, and parse responses for production workflows.
Authentication Flow
Generate a service token from your dashboard settings. Attach it to every request: Authorization: Bearer wl_prod_8a9b2c3d4e5f. Tokens expire after 90 days of inactivity and support IP allowlisting for enterprise tiers.
Payload Inspection Example
When querying GET /api/v1/logs/req_77829, the response returns a 200 OK with fields: timestamp (ISO 8601), method, status_code, headers (key-value map), body (raw string or parsed JSON), and response_time_ms. Use the X-WebhookLab-Signature header to verify webhook authenticity via HMAC-SHA256.