Data types

Interpret identifiers, dates, money, flags, and optional legacy fields.

Response fields reflect the existing application and database serializers. Some values that look numeric remain strings; other responses convert them to numbers. Parse the schema for each operation and avoid relying on one serializer’s behavior across all endpoints.

Identifiers

Event, order, attendee, and product IDs are UUID strings. Public shop slugs are human readable identifiers for URLs and are not substitutes for event UUIDs. Preserve IDs exactly when using them as map keys.

Dates and timezones

Event dates and ordinary record timestamps commonly use YYYY-MM-DD HH:MM:SS without an offset. Interpret them using the event or organization’s applicable timezone. Do not append Z and silently turn local event time into UTC.

Compact order snapshots use Unix seconds in d. Compact attendees use a text creation date in d and Unix seconds for the order creation time in od. pendingActionInitiatedAt uses an ISO 8601 timestamp or null.

Money and currencies

Product price can be a decimal string. Compact monetary fields such as t are decimal amounts in the event currency, not integer cents. Use decimal arithmetic and keep the currency alongside the amount. Consult the event’s VAT settings before presenting tax inclusive totals.

Flags and missing values

Legacy flags can be integers or numeric strings. Derived payment fields can be booleans. Optional compact fields may be omitted when empty; a missing p must not be confused with a guaranteed settled payment. Empty maps may serialize as []. Handle missing, null, and empty values separately.