Video view webhook

Video watch progress webhooks are separate from render / template finished webhooks you may configure elsewhere on your account. Only the URL you save with the endpoints below receives view-milestone events.

Requirements

On each request you need to provide your Bearer authentication token. See the Authentication section for more details.

POST /createVideoViewWebhookSubscription

https://api.repliq.co/v2/createVideoViewWebhookSubscription

Mandatory parameters

This endpoint requires the following parameters:

Response parameters

If the response status code is 200, the body includes:

DELETE /deleteVideoViewWebhookSubscription

https://api.repliq.co/v2/deleteVideoViewWebhookSubscription

Send DELETE to the URL in the code block above with the same Authorization header. No request body is required; the saved video-view webhook URL is cleared.

Response parameters

If the response status code is 200, the body includes:

HTTP errors (subscription endpoints)

When your webhook URL is called

When a lead watches a personalized video page, RepliQ sends HTTPS POST requests to your saved hookUrl with Content-Type: application/json. Each request is sent once per milestone per viewer session (same browser session), when that milestone is crossed for the first time.

So you can receive up to five POSTs for the same viewing session—one for started, then one each when 25%, 50%, 75%, and 100% are crossed for the first time.

Reliability and idempotency

• A down, slow, or error-returning receiver does not affect other RepliQ services; each delivery is isolated.
• A milestone is only treated as delivered after your endpoint returns 2xx. Non-2xx responses and network failures mean the same milestone may be attempted again on a later update.
• In rare cases the same milestone could be delivered more than once. Treat your handler as idempotent (safe to run twice for the same videoWatchPercentage + session), for example by deduplicating on (lead.videoUrl, videoWatchPercentage, occurredAt) or your own idempotency key.

Webhook body (JSON)

Example payload your endpoint receives:

{
  "videoWatchPercentage": "25",
  "occurredAt": "2026-03-22T06:08:03.673Z",
  "campaignName": "Spring outreach",
  "lead": {
    "videoUrl": "https://watch.example.com/videos/abc123",
    "leadWebsiteUrl": "https://prospect.example.com",
    "leadEmail": "jane.doe@example.com",
    "leadFirstName": "Jane",
    "leadLastName": "Doe",
    "jobTitle": "Marketing Director",
    "companyName": "Example Corp",
    "videoType": "website",
    "previewImgOrGifUrl": "https://cdn.example.com/previews/abc123_preview.gif"
  }
}

Automation tools (e.g. n8n, Zapier): The HTTP body is the JSON object above. Some UIs nest it under a property such as body—map fields from that object in your workflow.

Inside the lead object you will receive: