Find your signing secret

1. Open your parser and go to Settings → Integrations.
2. Under Added Integrations, expand Webhook export, then expand the endpoint you want.
3. You’ll see a Signing secret value. Use Copy to copy it.

This secret is different for every endpoint.

Headers sent with each request

Every webhook request includes these headers:

svix-id: <unique message id>
svix-timestamp: <timestamp in seconds>
svix-signature: <HMAC signature>

Your server should:

1. Read the raw HTTP request body as a string.
2. Read the three headers above.
3. Use the signing secret and headers to verify the signature.

Verifying in code

The easiest way to verify webhooks is to use the official Svix libraries. They handle all the details for you.

High‑level steps:

1. Install the Svix library in your backend (for example, using npm, pip, etc.).
2. Create a Webhook verifier with your endpoint’s signing secret.
3. Pass the raw body and headers to the verifier.
4. If verification fails, reject the request (e.g. return HTTP 400 or 401).

You can find language‑specific examples in the Svix docs:

• How to verify webhooks with the Svix libraries
• Manual verification details

Share those links, together with your signing secret, with your developer. They can plug verification into your existing server or workflow.

Response requirements

• Respond with 2xx (for example 200 OK) once you’ve successfully received the webhook.
• If you need to do heavy work, store the payload first and process it asynchronously so the response can be quick.