domain: ti.to · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Webhook Endpoint via the Admin API pointing at your receiving URL.
Subscribe to the specific event families you need — ticket.*, registration.*, checkin.*, and (as of Feb 2026) interested_user.* — as documented in the Admin API.
Check the Admin API's Headers section to confirm which headers Tito sends with each delivery for verification.
Use Tito's documented approach for receiving webhooks locally before pointing a webhook at a production endpoint.
Expect JSON object payload bodies for ticket.*/registration.*/checkin.* events, and treat metadata fields as JSON objects rather than JSON-encoded strings.
Known gotchas
The registration.started webhook was removed (8 May 2024) for GDPR reasons — don't build flows depending on partial/in-progress registration events.
The 'reminder' ticket state/webhook was dropped in the v3 Admin API (28 Sept 2023) and replaced by 'unassigned' — old integrations referencing 'reminder' tickets will break.
metadata changed from a JSON-encoded string to a native JSON object in March 2019 — old integration code that JSON-parses metadata as a string will now fail or double-parse.
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?