Frequently Asked Questions
Instant webhook debugging in real-time
Technical & Billing
Everything you need to know about WebhookLab’s infrastructure, data policies, and plan limits. Can’t find what you’re looking for? Contact our engineering team at support@webhooklab.io.
How long are webhook logs retained?
On the Starter plan, raw request and response logs are stored for 24 hours. Pro and Enterprise plans extend retention to 30, 60, or 90 days depending on your tier. All payloads are encrypted at rest using AES-256 and stored in our primary PostgreSQL cluster. You can also export logs to S3-compatible buckets via the API.
What are the limits on the free Starter plan?
The Starter plan includes 5,000 webhook requests per month, up to 3 active endpoints, and a 10 MB payload size limit per request. It does not include custom domain routing, rate limiting rules, or team collaboration features. Upgrade to Pro to unlock 100,000 monthly requests and 50 endpoints.
Does WebhookLab support custom SSL certificates?
Yes. When you attach a custom domain to an endpoint, WebhookLab automatically provisions and renews TLS certificates via Let’s Encrypt. For Enterprise customers, we support manual certificate uploads (PEM/CRT) and SNI configuration. All inbound traffic is enforced over TLS 1.3, with legacy 1.2 fallback disabled by default.
Where are your webhook endpoints hosted?
Our primary ingress clusters are located in Frankfurt (DE1), US East Virginia (VA1), and Singapore (SG1). Traffic is routed via Anycast DNS to ensure sub-50ms latency globally. We maintain automatic failover between regions, and Enterprise plans allow you to pin endpoints to a specific geographic cluster for data residency compliance.
Need a dedicated endpoint for high-volume production workloads?
View Enterprise Plans Read API Documentation