🔧 Change
Structured event data in orders
The API now supports structured event data on order line items. You can optionally provide an “eventInformation” section with details such as event name, dates, organizer, ticket type, and address to better match orders with external event systems. Existing orders without this information continue to work as before, and invalid values for event and ticket types are now rejected with a validation error.
🐛 Fix
PLEN-11373: When retrieving access right details, the createdByType and changedByType fields sometimes returned a customer ID instead of the expected type. These fields now return the documented values again (for example, “MERCHANT”), ensuring consistent and reliable results.
PLEN-11296: For orders that include a bonus, the PDF order confirmation could show incorrect shipping information. The PDF now displays the shipping instruction according to the configured delivery condition (for example, “after payment is received”).
PLEN-11262: When validating gift vouchers via the API, codes could be returned as valid even if they belonged to a different client. Voucher codes are now only considered valid for the client of the API key used; otherwise the code is returned as not found/invalid.
PLEN-11351: Some API requests were aborted too early and returned a 504 Gateway Timeout, even though processing would have completed shortly after. The timeout limits have been increased so requests have more time to finish under normal load and are less likely to fail with a timeout.