Webhook Payloads

Webhook payloads send lead data from Premium Qualified Leads to a buyer-owned endpoint.

Payload fields vary by vertical and buyer configuration. This article describes the common structure buyers should expect.

Example payload

{
  "delivery_id": "example_delivery_id",
  "lead_type": "funding",
  "delivered_at": "2026-01-15T18:30:00Z",
  "contact": {
    "first_name": "Example",
    "last_name": "Consumer",
    "phone": "+15555555555",
    "email": "consumer@example.com"
  },
  "location": {
    "state": "CA",
    "zip": "90001"
  },
  "qualification": {
    "requested_product": "example",
    "amount_range": "example"
  },
  "tracking": {
    "source": "example_source",
    "campaign": "example_campaign",
    "sub_id": "example_sub_id"
  },
  "compliance": {
    "consent_timestamp": "2026-01-15T18:29:30Z",
    "source_url": "https://example.com/landing-page",
    "trusted_form_url": "https://example.com/certificate"
  }
}

The exact payload for your account may be different.

Recommended buyer response

Buyers should return a fast success response after receiving and storing the lead.

Example success response:

{
  "success": true,
  "message": "Lead received"
}

Webhook best practices

Use HTTPS.
Respond quickly.
Store the delivery ID.
Log the full request internally.
Avoid rejecting leads because of optional fields.
Coordinate field changes before updating production systems.
Use test delivery tools before accepting production traffic.