Webhooks are how TruePlayer tells your other tools what happened, automatically and instantly.

Requires TruePlayer Pro.

What a Webhook Is

A webhook is a web address you give TruePlayer. Whenever something notable happens — someone finishes a video, passes a quiz, gets locked out — TruePlayer sends the details to that address.

You don’t need to understand the mechanics. Tools like Zapier and Make give you an address to paste in, and from there you build whatever automation you like:

• When someone completes the safety video → add them to the “certified” list and email their manager
• When someone fails a quiz twice → notify the course instructor
• When someone reaches 50% of the sales video → create a lead in the CRM
• When someone opts in inside the player → add them to a nurture sequence

The Events You Can Send

view.started fires on genuine playback, not merely on page load — so it reflects real views.

Add a Global Webhook

Global webhooks receive events from every video on your site.

Step 1: Open the Settings

Go to: TruePlayer → Settings → Global webhooks

Step 2: Add an Endpoint

Click Add webhook and fill in:

Step 3: Save

Click Save.

Add a Webhook to One Video

If you only want events from one specific video, add the endpoint on the video itself:

Open the media item → Interactions → Webhooks

The fields are identical. Per-video webhooks are sent in addition to your global ones.

Send a Test

Before you rely on an automation, confirm the other end is receiving properly.

• Click Send test next to your endpoint.
• Check the receiving tool for the sample delivery.

The test sends a payload in exactly the same shape as real traffic. A test that passes really does mean real events will be accepted — it isn’t a simplified stand-in.

Webhook Logs

Go to: TruePlayer → Settings → Webhook logs

Every delivery attempt is recorded:

That last part matters. When an endpoint rejects a delivery, the reply usually says exactly why — “required field missing”, “invalid token” — which turns a mystery into a five-second fix.

What the Data Looks Like

Each delivery carries the event details in a standard structure:

{

  “event”: “view.completed”,

  “video_id”: 123,

  “video_title”: “Safety Induction”,

  “email”: “[email protected]”,

  “name”: “Ada Lovelace”,

  “subject”: {

    “type”: “user”,

    “id”: “42”,

    “email”: “[email protected]”,

    “name”: “Ada Lovelace”

  },

  “coverage_percent”: 94.5,

  “timestamp”: “2026-08-26T12:00:00Z”,

  “site”: “example.com”

}

Quiz events also include the score, whether it passed, and which attempt it was.

The viewer’s email and name appear at the top level as well as inside the subject, because most automation tools expect to find them there.

Verifying it really came from you. Each request includes a signature built from your secret. If your receiving tool supports signature checking, it can confirm the delivery is genuine. Zapier and Make don’t require this — it is there for custom systems that want it.

Frequently Asked Questions