Webhook API

If you prefer to send conversion events from your server rather than the browser, you can POST directly to the Pruuv webhook endpoint. This is useful when you already have lead data in a CRM or backend system and want to forward it to Pruuv without adding JavaScript to your pages.

Authentication

All requests must include a Bearer token in the Authorization header. The token is the Webhook Token shown alongside each funnel stage in Connections > Funnel Webhooks.

Endpoint

POST https://app.pruuv.io/api/webhooks/funnel/{stageId}
Authorization: Bearer YOUR_WEBHOOK_TOKEN
Content-Type: application/json

Example request

curl -X POST https://app.pruuv.io/api/webhooks/funnel/YOUR_STAGE_ID \
  -H "Authorization: Bearer YOUR_WEBHOOK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "reference":    "CRM-REF-001",
    "utm_source":   "google",
    "utm_medium":   "cpc",
    "utm_campaign": "brand-search",
    "gclid":        "EAIaIQobCh...",
    "revenue_value": 250,
    "currency":     "GBP"
  }'

Payload reference

All fields are optional except reference.

Responses

Deduplication

Events with the same reference at the same stage within a 60-second window are deduplicated. Only the first call is recorded; subsequent identical calls within the window return { received: true, duplicate: true } with a 200 status. This makes it safe to retry on network errors.

Rate limits

The webhook accepts a maximum of 1,000 events per hour per funnel stage. Requests beyond this limit receive a 429 response.

Integration paths compared