Skip to content

Changelog

Versioning policy and release history for the ShowTix Partner API, webhooks and embeds.

For developersLast updated

On this page

What's changed in the ShowTix Partner API, and how we version it.

Versioning policy#

  • The major version is in the URL: /api/partner/v1.

  • Additive, non-breaking changes ship without notice — new endpoints, new optional parameters, new fields on objects, new webhook event types and new enum values in fields that document them as extensible. Your client must ignore fields and event types it doesn't recognise.

  • Breaking changes only ever ship in a new major version (/v2). The previous version stays available for at least 12 months after the new one launches, and we email every organisation with an active key before deprecation.

  • Every response carries a ShowTix-Version header — currently 2026-10-18 — and webhook payloads carry the same value in api_version.

History#

2026-10-18 — Partner API v1 launched#

  • Events, ticket types and venues (events:read).

  • Checkout sessions with hosted checkout, orders and tickets (orders:read, orders:write).

  • Comp ticket batches, attendee lists and door check-ins (attendees:read, check_in:write).

  • Signed webhooks for 11 event types, plus webhook endpoint management (webhooks:manage).

  • Live and test keys, IP allowlists, key rolling, idempotency keys, cursor pagination and updated_since sync.

  • OpenAPI 3.1 document at GET /openapi.json.

  • Every event belongs to exactly one organisation: keys and webhooks only ever see events created under their own organisation.

  • Embeddable checkout (/embed/v1.js), branded storefronts at your-name.showtix.com.au and custom-domain verification.

Questions about a change? Email support@showtix.com.au.

Was this article helpful?