Ticket Tailor

Ticket Tailor pet for OpenPets.

This pet uses a hand-authored OpenAPI specification derived from the official Ticket Tailor REST docs at https://developers.tickettailor.com/docs/api/ticket-tailor-api.

Status

This is an initial scaffold focused on high-value read endpoints plus a connection check. The underlying spec can be expanded over time as more request and response details are captured from the docs.

Setup

1. Generate an API key in your Ticket Tailor box office settings.
2. Add it to .env:

TICKET_TAILOR_API_KEY=your_api_key_here

Authentication

Ticket Tailor uses HTTP Basic Auth with the API key as the username and an empty password. The pet config uses basicAuthFormat: "apikey-colon" so requests are sent as Authorization: Basic base64(api_key:).

Included API Areas

• ping and overview
• events and event series
• orders and issued tickets
• membership types and issued memberships
• discounts, holds, checkout forms, products, stores, vouchers, and voucher codes
• check-ins, overrides, and waitlist signups

Commands

bun run generate
bun run build
bun run test:connection

Notes

• The official Ticket Tailor docs do not currently expose an OpenAPI or Swagger document.
• This pet uses a local openapi-spec.yaml file so the spec can evolve inside the repository.
• Ticket Tailor rate limits the API to 5000 requests per 30 minutes, with lower limits on some endpoints.