Breaking Changes

Important:

This documentation applies exclusively to the latest version of the Attendee API, which represents the current ADITUS standard.
If the API endpoint URL you received from your Customer Success Manager does not end with /terp/v1/events/:event/attendees, your system does not provide the latest Attendee API. The information below only applies to the new version.

If you are upgrading from an older version to this new API, please review the following breaking changes:

---

Breaking Changes Overview

1. API Endpoint

• The URL for the Attendee API has changed.

• There is now a single endpoint for all use cases:
  GET {{API_BASE_URL}}/terp/v1/events/[EVENT_ID]/attendees

2. JSON Result Structure

• attendee

  • PersonContactPhoneNumber → permanently removed. Use phone instead.

  • PersonContactMobileNumber → permanently removed. Use mobile instead.

• booth

  • BoothNumber → permanently removed. Use number instead.

  • BoothHall → permanently removed. Use hall instead.

  • BoothStand → permanently removed. Use stand instead.

  • BoothExternalId1 → permanently removed. Use externalId1 instead.

  • BoothExternalId2 → permanently removed. Use externalId2 instead.

  • BoothExternalId3 → permanently removed. Use externalId3 instead.

• Batch Query

  • The structure has changed:

    • Previously, booth and exhibitor were also present in the registration object.

    • Now, this information is consistently found in the ticket object, as in other endpoints.

    • Example:

      • Old: registrations[].booth

      • New: registrations[].ticket.booth

3. Event Identification

• Requests can now only be made using the unique ID (GUID) of the event.

• The use of the internal event ID is no longer supported.

• You must always provide a valid event GUID for attendee queries.

4. Ticket Links

• GoogleWallet

  • Now only available if the GoogleWalletFeature is enabled and the medium itself is active.

• Wallet

  • Now only available if the medium is active.

• mTicket

  • Now only available if the medium is active.

5. Query Parameters

• CustomFieldsLookupLanguageId has been renamed to CustomFieldsLookupLanguage and now expects an ISO2Code.