Changelog

When creating a category via the API without specifying a color, we now default to colors from our updated palettes.

Concurrent API calls cannot create events with duplicate keys anymore. Existing duplicates have been renamed to <original key>_DUPLICATE

Passing in a social distancing ruleset when creating or updating an event has no effect

Channels can be passed in when creating an event

We only return status changes from the last 365 days

Chart reports now return isAccessible, isCompanionSeat and hasRestrictedView fields for seats

Status changes for areas with many holds are now much faster

Made pushing real-time status updates faster under heavy load

Added call to completely replace the channels on an event (including the assigned objects)

Deprecated /events/{eventKey}/channels/assign-objects. Use /events/{eventKey}/channels/replace instead.

We now make a distinction between calls in the priority lane and in the regular lane. Priority lane calls are typically used during ticket sales (changing object status, creating a hold token...). They have a higher rate limit than regular calls.

Backend: more fine-grained rate limiting. Some endpoints (Reporting endpoints and endpoint to fetch the status changes log) have a stricter rate limit, to free up capacity for endpoints that are used for ticket sales.

Allow adding multiple channels at once

Reporting calls on events in seasons with channels are much faster now

Reporting calls now have a lower rate limit than other ones