Record and audit attendee check-ins for a Ticket Tailor event via the Check Ins API
domain: tickettailor.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to the create-check-in endpoint with the issued ticket identifier to mark an attendee as checked in at the door.
GET /v1/check_ins (paginated) to pull a full check-in log for reconciliation after the event.
Cross-reference check-in records against /v1/issued_tickets to flag tickets that were never scanned.
Use cursor pagination (starting_after/ending_before) when the check-in log spans many pages.
Known gotchas
Check-ins are additive records tied to a ticket, not a toggle — re-scanning doesn't 'undo' a prior check-in through this endpoint.
Like other Ticket Tailor resources, check-in records are scoped to the box office tied to your API key — you can't check in or list tickets belonging to a different box office with the same key.
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?