Attendees
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_ID]/attendees, your system does not provide the latest Attendee API. The information below only applies to the new version.
Introduction
Across many projects, there has been a consistent need for a consolidated interface to access attendee data. Previously, diverse, customer‑specific integrations with varying data formats limited reusability and increased maintenance effort.
The Attendee endpoint provides a general interface that enables standardized and secure retrieval of attendee data from ADITUS events and is intended to gradually replace existing bespoke solutions.
Authentication
The ADITUS Attendee end point use basic authentication (key/secret).
Fair event
The attendee data can only be requested via the context of the fair event for example:
-
by internal identifier (event-id) :
- /api/terp/v1/events/{{eventId}}/attendees
Query-Parameters
All query parameters within the Attendee API are case-insensitive. (TicketCode = ticketCode = ticketcode)
Definition of canceled or blocked tickets
-
A canceled ticket means that the associated sales transaction has been canceled.
-
There can be various reasons why a ticket has been blocked. In most cases, the corresponding trade fair appearance has been canceled or the ticket order has been revoked, which means that tickets are no longer valid for entrance.
-
A canceled ticket is also a blocked ticket. A blocked ticket does not necessarily have to be canceled.
Timestamps and time zone
All timestamps are presented in German local time (CET/CEST). Daylight‑saving changes are applied automatically. The timestamps themselves do not contain explicit time zone information and always show only the locally valid German time.
Hints
The ADITUS Attendee end point are only intended solely for server-to-server communication. They must not be used in any client application where third parties could potentially access the data.