- How long do temporary webhook testing URLs remain active?
- Webhook URLs remain active for 24 hours of inactivity. You can generate new endpoints with one click whenever needed.
- Can I test webhooks sent by Stripe, GitHub, Shopify, and Slack?
- Yes. The endpoints accept standard HTTP/HTTPS POST, PUT, PATCH, and GET calls from any external service.
- Does the tester support customizing HTTP response status codes and headers?
- Yes. You can configure custom return status codes (200, 201, 400, 500) and response bodies to simulate success or error handling.
- Is my webhook payload data secure and private?
- Yes. Endpoints are protected with random cryptographic UUIDs, and event payloads are stored ephemerally in memory without permanent persistence.
- How do I test sending requests to an external webhook URL?
- Paste your external webhook URL (such as a Discord channel webhook, Slack incoming webhook, Zapier/Make hook, or custom API endpoint) into the destination URL bar, choose your HTTP method (POST, PUT, PATCH, DELETE), select a template or write custom JSON, and click "Send Webhook". Cerilas dispatches the request and displays the HTTP status code (e.g. 200 OK), roundtrip latency, response headers, and response body.
- How do I send a test webhook to Discord or Slack?
- Click the "Discord Webhook" or "Slack Webhook" template button above the URL bar. This pre-fills an authentic JSON payload with rich embeds, markdown blocks, and author avatars. Paste your Discord or Slack webhook URL and click Send. The message will appear instantly in your channel with real-time delivery confirmation.
- How does HMAC-SHA256 signature generation work for secure webhooks?
- Many webhook consumers (e.g. Stripe, GitHub, Shopify, custom microservices) require incoming requests to include an HMAC signature header to verify authenticity and prevent tampering. In the "HMAC Signature" tab, enter your secret key. Cerilas calculates the SHA-256 hash of your exact JSON payload and attaches the signature header (e.g. X-Hub-Signature-256 or Stripe-Signature) automatically.
- Can I test webhook concurrency, queuing, and rate limits with repeated requests?
- Yes! Open the "Repeat" tab to configure multi-call stress testing. You can dispatch up to 20 sequential webhook calls with customizable delays (e.g. 200ms interval) to test your backend queue workers, idempotency keys, and rate limiters.
- What dynamic variables can I use in my webhook payloads?
- You can insert dynamic placeholders like {{timestamp}} (current epoch ms), {{iso_date}} (ISO-8601 timestamp), {{uuid}} (random v4 UUID), and {{random_id}} (random 6-digit number). These placeholders are automatically evaluated and replaced with fresh values each time a webhook is dispatched.
- Why use Cerilas Webhook Tester instead of Postman or cURL?
- Cerilas Webhook Tester runs directly in your browser with zero download, zero sign-in, and zero bloat. It features dedicated 1-click webhook templates for Discord, Slack, Telegram, Stripe, and Zapier, dynamic placeholder generation, automatic HMAC signature computation, and a dual-purpose temporary test receiver for full end-to-end debugging.