ADITUSAPI
ÜbersichtAnwendungsfälleLive-DemoAPI-ReferenzTeam
API-Keys
Modules
▾Introduction
Guidelines
General
HTTP verbs
Status Codes
Result codes and messages
Authentication and Authorization
Just Entrance
Ticket purchase & registration
Byndr
Survey
Assets
Webhooks
Exhibitors
Attendees
ADITUS/Guidelines

Guidelines

Subsections#subLink copied

General Request structure All URIs and their underlying operations are resource based. The structure of the URIs is as follows: product/version/area/sub-area(s)/resHTTP verbs GET GET will read data. Data can be a list or single object of a resource. - GET causes a 404 if the resource or endpoint could not be found - GET causeStatus CodesHttp codes can be separated in 4 simple groups: - codes for successful calls, - calls redirected to new or moved URI, - client and - server sideResult codes and messagesError codes are reserved up to 10.000, ensuring a dedicated range and reserving space for future codes. The range starting at 10,001 is reserved for TERP v5. VAuthentication and AuthorizationAll endpoints for this area can only be accessed if the client of the API is authenticated. A client is authenticated via the ADITUS identity provider (IdP) wit
ADITUS

One API for tickets, entrance, and marketing — built in Hannover since 1998.

Navigation
  • Overview
  • Use cases
  • Live demo
  • API Reference
  • ADITUS-Queue
API
  • Just Entrance
  • Discovery
  • Cart & checkout
  • Webhooks
  • Attendees
Company
  • Team ADITUS
  • Imprint
© 2026 ADITUS GmbH · Hannover, Germany · since 1998SOC 2 · ISO 27001 · GDPR · PCI DSS L1