API-Zugang anfragen

The ADITUS API reference

565 endpoints across 10 product modules — ticketing, entrance control, networking, surveys, exhibitors, and more. Production-ready from day one.

10
Modules
565
Endpoints
v1+
Stable versions
JSON
Response format

Getting started#start

The ADITUS-System provides many API products, tools, and resources that enable you to to streamline the ticket purchasing and entrance management process for events, attractions, and venues
Getting started guide

  • The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources.

  • The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key.

Browse modules#modules

IntroductionYour starting point for the ADITUS API: what the platform covers, how the sections fit together, and where to begin your integration.GuidelinesThe API's conventions: request and URI structure, authentication via Basic or OAuth, HTTP verbs, status codes, and the shape of every response.Just EntranceADITUS hardware can be used with external registration vendors.2Ticket purchase & registrationThe Shop API deals with requests concerning shop processes.77ByndrByndr is a product API designed to enable seamless, secure connections between event attendees through badge (QR code) scans.9SurveyA survey is an instrument for systematic data collection.9AssetsPlease prefer using this API section over the deprecated theme API.7Webhooks🚀 Connect your ticket shop with your favorite apps!ExhibitorsEndpoints in this module.4AttendeesImportant: This documentation applies exclusively to the latest version of the Attendee API, which represents the current ADITUS standard.5