Authenticate to the Ticket Tailor API with HTTP Basic Auth and handle its per-hour rate limits
domain: tickettailor.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an API key in the Ticket Tailor box office API settings; each key is scoped to a single box office.
Base64-encode the API key and send it as the username in an HTTP Basic Auth Authorization header (password left blank), or pre-build the 'Authorization: Basic ...' header yourself.
Send 'Accept: application/json' on every request against the production base URL https://api.tickettailor.com.
Read the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset response headers to track usage against the roughly 5000-requests-per-30-minutes cap.
Handle 429 responses by honoring the Retry-After header before retrying.
Known gotchas
The issued-memberships creation endpoint (POST /v1/issued_memberships) has its own tighter limit of 30 requests/hour, separate from the general cap.
TLS 1.2+ is required; older TLS clients will fail the handshake.
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?