integrate tiqets inventory via the distributor api for product catalogue, availability, and bookings
domain: developers.tiqets.dev · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
become a Tiqets partner by contacting Tiqets affiliates support; self-generated API keys initially only unlock the catalog (products) and availability endpoints, advanced/booking access requires Tiqets to review and approve your request
generate API keys from the Tiqets partner portal under Tools > API tokens, and send the key as an 'Authorization: Token <API_key>' header on every request
use the Content API and Availability & Pricing API (GET /products/{productId}/availability) to fetch product listings, opening times, live availability, and pricing (max 31 days of availability per request, up to 1 year out)
to book, sign requests per Tiqets' JWT signing guide, then call POST /orders (Create Order, which reserves for 30 minutes) followed by Confirm Order; use Get Order Information, Retrieve Tickets, or Cancel Order as needed
before production Booking API access is granted, pass Tiqets' recorded-demo acceptance process against the Test environment (e.g. create/confirm orders for test products, plus a cancellation) and submit the recording to Tiqets API support
subscribe to Product Change Notifications (PCN) webhooks and the Order Change Notification webhook to stay in sync with off-sale/availability and order-status changes
Known gotchas
the Distributor/Booking API is partner-gated end-to-end: baseline API keys only cover catalogue/availability, and placing real bookings requires manual partner approval plus a recorded integration demo before production access is unlocked
orders created via POST /orders are non-confirmed reservations that automatically expire after 30 minutes if not confirmed via the Confirm Order endpoint
only a fair-use rate limit currently applies (not a hard documented cap), but Tiqets states it may enforce stricter limits in the future, so integrations should still implement backoff/caching
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?