Issue and void individual tickets directly (outside a checkout order) using Ticket Tailor's Issued Tickets API
domain: tickettailor.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /v1/issued_tickets with an event_id and ticket_type_id to draw from an occurrence's ticket-type allocation, or supply a hold_id to issue from a pre-existing hold.
Note that an issued ticket created this way is not attached to a customer order.
GET /v1/issued_tickets (paginated) or GET a single issued ticket by ID to look them up.
Call the void-issued-ticket endpoint for a specific ticket ID when it needs to be revoked.
Use starting_after/ending_before cursor pagination (max limit 100) when listing large result sets.
Known gotchas
Issuing a ticket via the API consumes one credit even if the ticket price is free.
The request fails if the ticket type is a seated type tied to a seating chart, or if no inventory remains.
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?