Automation integration
Turn on webhooks for a video, and when the view ends Mindstamp posts the view, each interaction, and, for a known viewer, a one-time lead record to your URL as signed JSON. View webhooks start on the Core plan, and interaction and lead webhooks start on Pro.
What reaches Webhooks
| Record | When Mindstamp sends it | What the JSON holds | Plan |
|---|---|---|---|
| View | Once for each completed view. | Watch progress, scores, viewer details, location, device, variables, and every interaction and answer in the view. | Core and higher |
| Interaction | One POST for each interaction in the view, all sent after the view ends. | The interaction type and value, the answer and correct answer, the time in the video, viewer details, and variables. | Pro and higher |
| Lead | When a known viewer’s view ends. After one successful send, never again for that viewer. | Name, email, phone, custom ID, viewer totals, and variables. | Pro and higher |
Set it up
Account
Each video
Webhooks and Mindstamp
Other Mindstamp routes
Added by Mindstamp
Limits
Questions
Three record types. A view record has the watch progress, scores, viewer details, and every answer in the view. An interaction record has one answer or click. A lead record has the viewer’s name, email, phone, and totals. Each is a JSON POST. See how Mindstamp webhooks work for every field.
No. Mindstamp sends all three types in background processing after the view ends, with no fixed delivery time. To act on each answer as it happens, listen for player events on your page instead. Player events start on the Core plan.
Each request has an X-Mindstamp-Timestamp header and an X-Mindstamp-Signature header in the form t=timestamp,v1=signature. The signature is an HMAC-SHA256 of the timestamp, a period, and the raw body, made with your webhook key. Compute the same value on your server and compare the two.
View webhooks start on the Core plan. Interaction and lead webhooks start on Pro, and so does the REST API. API tokens need a paid plan, so the REST API does not work during a trial. Webhooks do. See pricing.
View and interaction webhooks fire for anonymous viewers too. A lead webhook needs a known viewer, with a name, email, phone, or custom ID. Most videos get one from lead capture.
Yes, through your own code or an integration service that receives the POST and writes the record. Mindstamp has no Salesforce setting in the app. See Salesforce and Mindstamp for the options.
Related
Help
Payload fields, headers, signing, and delivery rules.
Explore →Developers
Read views, viewers, and interactions with a token, on Pro and higher.
Explore →Help
Listen for plays, answers, and clicks in the browser as they happen.
Explore →Automation and data
Start a Zap from a new view, interaction, or lead, and send the data to the other apps you use.
Explore →Reporting
See every view, answer, and click in Mindstamp, whatever you send to other tools.
Explore →Feature
Ask for a name and email inside the video, so a view can belong to a known person.
Explore →Sources
Each link opens the page we used for the steps, versions, and limits above.
Mindstamp API reference
Mindstamp API reference
Mindstamp API reference
Mindstamp API reference
Facts checked October 12, 2026 against the Mindstamp app. Before you rely on a webhook, play one test view and check the request on your endpoint.
Connect it
Start a trial, turn on a view webhook for one video, and watch the first POST arrive.