# Versive Webhooks

Versive ([getversive.com](https://getversive.com/)) signs every webhook delivery following
Standard Webhooks, with the delivery provider's (Svix)
`svix-*` header names. Each delivery is an HTTP `POST` with a signed JSON body and three headers:
`svix-id`, `svix-timestamp`, and `svix-signature`. The body is
`{ "event_type": "interview.completed", "interview": { ... }, "study": { ... } }`. It has no event
id (use `svix-id`), and no header carries the event type.

**Webhooks are set up by Versive, not self-serve.** Hookdeck's configuration alert for this source
reads: "Versive support sets up webhooks. Ask them for the endpoint's signing secret." Email
support@getversive.com to provision the organization-level destination and get the secret.

## When to Use This Skill

* How do I receive Versive webhooks?
* How do I verify Versive webhook signatures (`svix-signature`)?
* How do I handle the `interview.completed` event?
* Where do I get the Versive webhook signing secret?
* Why is my Versive webhook signature verification failing, or rejecting Hookdeck retries?

## Verification (core)

Signed content is `{svix-id}.{svix-timestamp}.{raw body}`. Svix signs it with HMAC-SHA256 using
the base64-decoded secret (the part after `whsec_`), base64-encodes the result, and sends one or
more space-separated `v1,<signature>` entries. Use the official `svix` library, which compares in
constant time. Read the `svix-*` headers, and when `svix-id` is absent fall back to the `webhook-*`
headers (`webhook-id`, `webhook-timestamp`, `webhook-signature`).

```javascript
import { Webhook } from 'svix'; // svix 2.x is ESM-only

const prefix = req.headers['svix-id'] ? 'svix' : 'webhook';
const id = req.headers[`${prefix}-id`];
const timestamp = req.headers[`${prefix}-timestamp`];
const signature = req.headers[`${prefix}-signature`];
// rawBody: the raw Buffer/string, never re-serialized JSON
new Webhook(process.env.VERSIVE_WEBHOOK_SECRET).verify(rawBody, {
  'svix-id': id, 'svix-timestamp': timestamp, 'svix-signature': signature,
  'webhook-id': id, 'webhook-timestamp': timestamp, 'webhook-signature': signature,
}); // throws on a bad signature or a timestamp outside the window
const event = JSON.parse(rawBody.toString('utf8')); // parse only after verify passes

```

```python
from svix.webhooks import Webhook, WebhookVerificationError

wh = Webhook(os.environ["VERSIVE_WEBHOOK_SECRET"])  # "whsec_..."
wh.verify(raw_body, {"svix-id": id, "svix-timestamp": ts, "svix-signature": sig,
                     "webhook-id": id, "webhook-timestamp": ts, "webhook-signature": sig})

```

> **For complete handlers with tests**, see [examples/express/](https://github.com/hookdeck/webhook-skills/tree/main/skills/versive-webhooks/examples/express/), [examples/nextjs/](https://github.com/hookdeck/webhook-skills/tree/main/skills/versive-webhooks/examples/nextjs/), [examples/fastapi/](https://github.com/hookdeck/webhook-skills/tree/main/skills/versive-webhooks/examples/fastapi/).

Each endpoint has one signing secret ("your endpoint secret"), handed over by Versive support when
the destination is provisioned. Versive doesn't print its format, but Svix secrets look like
`whsec_<base64>`, so keep the full value in `VERSIVE_WEBHOOK_SECRET`. Handlers fail closed: with
the variable unset (or not a `whsec_` value) they return 500 instead of accepting anything.
Versive's docs say to "reject stale timestamps" without a number. The `svix` library reads either
header-name set, so no mapping is needed beyond the fallback shown.

### Hookdeck retries and replays hit the 5-minute window

The `svix` and `standardwebhooks` libraries always enforce a fixed 5-minute timestamp window, and
it can't be configured. Hookdeck retries and replays resend the **original** `svix-timestamp`, so
the library rejects any retry or replay that happens more than 5 minutes after the original
delivery. If you verify behind Hookdeck (or replay old events), use the manual verifier in
[references/verification.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/versive-webhooks/references/verification.md), where the window can be dropped or
widened. Deduplicate on `svix-id` instead of relying on the timestamp.

## Common Event Types

One event is documented (the list may not be exhaustive). The name is `event_type` in the JSON
body, and the examples handle it and acknowledge anything else with `200`:

| Event | Triggered When |
| --- | --- |
| `interview.completed` | A participant completes an interview (screened-out interviews are excluded) |

The `interview` object can carry transcripts and recordings: treat the request as sensitive and log
only what you need. See [references/overview.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/versive-webhooks/references/overview.md) for the payload shape.

## Environment Variables

```bash
# Endpoint signing secret from Versive support (Svix format, starts with whsec_)
VERSIVE_WEBHOOK_SECRET=whsec_xxxxx

```

## Local Development

```bash
# Start tunnel (no account needed)
npx hookdeck-cli listen 3000 versive --path /webhooks/versive

```

Ask Versive support to point the organization's webhook at the tunnel URL, then complete an
interview in a study to receive a real `interview.completed` delivery.

## Reference Materials

* [references/overview.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/versive-webhooks/references/overview.md) - Versive webhook concepts, the interview.completed event, payload shape, delivery
* [references/setup.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/versive-webhooks/references/setup.md) - Get Versive support to provision the webhook, obtain the secret
* [references/verification.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/versive-webhooks/references/verification.md) - Svix verification details, header fallback, manual verifier, timestamp window