From version 4.135 onwards

New Features and Enhancements from Version 4.135

Starting with version 4.135, the Attendee API introduces several important enhancements to improve data protection, transparency, and operational flexibility for partners and integrations. These changes ensure that data access is more granular, event-specific, and compliant with current business and privacy requirements.

---

Key Enhancements

1. Role- and Article-Based Data Access

• Fine-grained access control:
  Third parties can only access attendee registrations for the specific badge categories (articles) and user roles that have been explicitly granted to them. For example, a matchmaking provider may only receive data for VIP and Exhibitor categories.

• Standardised roles:
  The API supports a standard set of badge category roles, such as Visitor, Exhibitor, Press, Services, and more. If there are additional badge categories in the system used, corresponding roles must also be created in the system. Please note the naming convention for roles!
  Example roles include:

  • ApiAttendeeBadgeCategoryCONTRACTOR

  • ApiAttendeeBadgeCategoryCREW

  • ApiAttendeeBadgeCategoryDELEGATE

  • ApiAttendeeBadgeCategoryEXHIBITOR

  • ApiAttendeeBadgeCategoryMEDIA

  • ApiAttendeeBadgeCategoryORGANIZER

  • ApiAttendeeBadgeCategoryPRESS

  • ApiAttendeeBadgeCategorySPEAKER

  • ApiAttendeeBadgeCategorySPONSOR

  • ApiAttendeeBadgeCategorySTAFF

  • ApiAttendeeBadgeCategorySTUDENT

  • ApiAttendeeBadgeCategoryVIP

  • ApiAttendeeBadgeCategoryVISITOR

  • ApiAttendeeBadgeCategoryNONE

    • for all articles that do not have a BadgeCategory

If one of these new roles is configured, all other articles will be filtered out. BadgeCategory roles can be combined.

2. Block-Scoped Payloads

• Modular response structure:
  The API response is organised into logical blocks (such as attendee, address, customFields, termsOfService, ticket, article, booth, exhibitor, additionalSalesInformation).
  Each block can be enabled or disabled based on the assigned user role.

• Default behaviour:
  If no specific role configuration is set, a baseline set of blocks is returned (e.g., attendee, address, customFields, ticket, article, booth, exhibitor)

  • the same as before version 4.135

• Full access roles:
  Special roles are available to grant full access to all attendee or ticket blocks:

  • ApiAttendeeWithAttendeeFullAccess (includes all attendee-related blocks)

    • ApiAttendeeWithAttendeeInformation

    • ApiAttendeeWithAddressInformation

    • ApiAttendeeWithCustomFieldsInformation

    • ApiAttendeeWithTermsOfServicesInformation

    • ApiAttendeeWithUserInformation

  • ApiAttendeeWithTicketFullAccess (includes all ticket-related blocks)

    • ApiAttendeeWithTicketsInformation

    • ApiAttendeeWithArtcleInformation

    • ApiAttendeeWithBoothInformation

    • ApiAttendeeWithExhibitorInformation

    • ApiAttendeeWithBarcodeInformation

    • ApiAttendeeWithTicketLinksInformation

If one of these new roles is configured, all other areas that are not configured will be deactivated. Roles can be combined.

4. Consent and Terms Metadata

• Transparency and compliance:
  The API now includes metadata about the version of the Terms of Service and Privacy Policy that each user has accepted, including the identifier and timestamp.

5. Additional Address Attribute

• Expanded address information:
  The payload now includes the stateOrProvince attribute for attendee addresses.

6. 1:N Short Code

• Short code support:
  The API now includes 1:N short codes in the attendee payload.

7. Request by Ticket Unique ID

• Flexible querying:
  Attendee data can now also be requested using the unique ticket ID.

• New optional query parameter

  • Indicates whether the provided ticket code should be interpreted as a ticket barcode. Set this parameter to true (the default is false) when searching for non-ADITUS tickets whose barcode value is a GUID. Otherwise, every GUID is interpreted as an ADITUS ticket unique ID.

8. Additional User Attributes

• Extended user information:
  The attendee payload now includes a new user object with the following attributes:

  • uniqueId

  • number

  • externalId1

  • externalId2

  • externalId3

  • lastActionOn

9. Unique IDs for All Entities

• Consistent identification:
  Unique IDs are now available for all relevant entities, including:

  • FaireventAppearances (UniqueId and Number)

  • Exhibitor (UniqueId and Number)

  • Buyer (UniqueId)

---

Summary of Improvements

• Privacy by design: Only authorised partners see the data relevant to their assigned roles and articles.

• Event-specific data: Terms of Service and Privacy Policy answers are strictly scoped to the relevant event.

• Operational clarity: Structured payloads and additional attributes improve integration and monitoring.

• Future-ready: The new structure supports further enhancements and performance improvements.