Your server gets every Influtics event
Register one HTTPS endpoint and get creator, video, and stats events as signed JSON.
- Signed POST on every event
- 4 event types
- Test ping included
- Same id across retries
what your server receives
POST your-url HTTP/1.1
X-Influtics-Event: video.created
X-Influtics-Delivery-Id: 3f2b0c9e-…
X-Influtics-Signature: ts=1763456122;h1=9f86d081…
{
"id": "3f2b0c9e-…",
"type": "video.created",
"organization_id": "9f1d2b6e-…",
"occurred_at": "2026-11-18T09:15:22.418Z",
"data": { "video_id": "6c2a0f4e-…", … }
}Events for the full journey of your video
Subscribe to all four or just the ones you consume. Every retry of a delivery carries the same body.
Video tracked
video.created
A new video was registered
Stats collected
Views, likes, comments land
stats.updated
Fresh numbers for the video
Your server
signed POST in, 200 out
Every event above is POSTed here as a signed delivery. creator.tracked fires when tracking starts; video.deleted when a video goes away. The full catalog:
| Event | What it carries |
|---|---|
| creator.tracked | Tracking started for a creator. Carries the blogger id, the platform, and the channel username. |
| video.created | A new video was registered. Carries the video id, the blogger id, and the external video id. |
| stats.updated | Fresh numbers arrived for a tracked video. Carries the video id and the external video id. |
| video.deleted | A tracked video went away. Carries the video id, the blogger id, and the external video id. |
Verify with the raw body
Recompute the signature over the timestamp plus the raw bytes, compare in constant time, allow five minutes of skew.
delivery shape
signed = ts + ":" + rawBody key = base64(secret) // 32 bytes h1 = hmac_sha256(key, signed)
verify.js
import crypto from 'node:crypto'
const key = Buffer.from(secret, 'base64')
const expected = crypto
.createHmac('sha256', key)
.update(ts + ':' + rawBody, 'utf8')
.digest('hex')
const ok = crypto.timingSafeEqual(
Buffer.from(expected, 'hex'),
Buffer.from(h1, 'hex'),
)After a rotation, try the current secret first, then the previous one for 24 hours.
Get Started
Save your HTTPS endpoint in Settings → Integrations → Webhooks, tick the events you want, copy the secret shown once, verify one test ping, then write your handler. The endpoint setup itself takes about ten minutes.
Setup in App
Requirements:
- Active Influtics account with an admin role
- Public HTTPS endpoint on a stable hostname
- Code that reads the raw request body before parsing
Questions receivers ask
Related Integrations
Explore other integrations that work seamlessly with Webhooks.

REST API
Pull any influencer data on demand with the REST API — the complement to webhook pushes.

n8n
Bring Influtics into visual workflows — trigger n8n flows from webhooks or poll with the node.
Start Using Webhooks Integration Today
Connect Webhooks with Influtics and start tracking your influencer marketing campaigns with powerful analytics.
100K+
Videos Tracked
50M+
Data Points Analyzed
99.9%
Uptime