Skip to content

Changelog

What changed for developers. We add an entry here when a change reaches production.

We only add to the /external/v1 routes. We add fields and routes without notice, so make sure your code ignores fields it does not know. If we ever need to remove or change something, we will tell you first, with a date.

November 2026

  • Webhooks: we can tell your server when an order, a reservation or a guest changes.
  • GET /external/v1/events/:id/ticket-types answers what a guest could buy for an event. GET /external/v1/events/:id and GET /external/v1/venues/:id read one row, and a venue answers its currency, opening hours and policies. See Show events and tables.
  • The field groups orders:payments and reservations:payments add each refund and dispute. See Refunds and disputes.
  • GET /external/v1/orders, reservations and guests: copy your data with one key, and read what changed since your last run. See Sync orders, reservations and guests.
  • A guest who replies STOP or START now comes back in GET /partners/sync/users, so your systems hear about it. See Keep your data in sync. Opt-outs from before November 5 do not come back by themselves.
  • This site is new. It replaces our earlier data sync page, and it corrects a few things that page said:
    • We do not store a "last synced" time for you. You keep your own checkpoint.
    • The order feed returns new orders. It does not bring an order back when it changes later.
    • There is no rule of one call a day. See Rate limits.