Send server-side events to TikTok Events API (v1.3)
domain: business-api.tiktok.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a TikTok for Business access token and your pixel ID from the TikTok Events Manager.
Construct a POST request to https://business-api.tiktok.com/open_api/v1.3/event/track/ with Content-Type application/json.
Set the Authorization header to YOUR_ACCESS_TOKEN.
Build the request body with pixel_code set to YOUR_PIXEL_ID, event set to the event name (e.g., Purchase), event_time as a Unix timestamp, and a properties object with relevant event data.
Include user identification signals in the user object (hashed email, phone, IP, user agent) to maximize match quality.
Inspect the response code field; a value of 0 indicates success.
Known gotchas
The correct v1.3 endpoint is /open_api/v1.3/event/track/ — the older /pixel/track/ path was the pre-v1.3 endpoint and should not be used for new integrations.
All personally identifiable user data (email, phone number) must be SHA-256 hashed before inclusion in the request body.
Event deduplication between browser-side pixel events and server-side API events requires matching event_id values; omitting event_id can lead to double-counting in reporting.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?