Request API access

Ticketing & marketing,
wired up intelligently.

One API for ticket sales, entrance management, and marketing activation — with the clarity your CTO expects.

Read the quickstart →ExamplesOpen in Postman
18ms
P50 latency
99.99%
Uptime '25
565
Endpoints
10
Sections
1B+
REQ/YEAR
●POST /terp/v1/import/ticketowners
curl {{API_BASE_URL}}/connect/token \
  -u $CLIENT_ID:$CLIENT_SECRET \
  -d "grant_type=client_credentials&scope=Shop"

# → returns access_token

curl {{API_BASE_URL}}/shop/v1/discovery/events \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Accept-Language: de-DE"
Demo system
Live status
Checking…
API…
Database…
Response time…
Last checked: —
Trusted & integrated by
Deutsche TelekomDeutsche MesseMesse FrankfurtMesse EssenMesse StuttgartDeutsche Landwirtschafts-Gesellschaft (DLG)NürnbergMesseMesse BremenMesse MünchenMesse Offenburg-OrtenauRX Global
Built for technical decision-makers

Six things your integration team will actually thank you for.

Designed for CTOs and platform teams — authentication, localization, webhooks, and idempotency without workarounds.

OAuth 2.0 client credentials

Mint short-lived bearer tokens with scoped claims like Shop or TERP. Rotate freely — sessions stay live.

AUTH

Localized by design

Pass Accept-Language and every textual field comes back translated. Cultures cascade through cart and checkout.

i18n

Quicodes & ticket links

Generate scannable QR payloads with one flag. Built-in regex categories sort scans into your reporting.

ACCESS

Real-time webhooks

30 events on tickets, carts, payments and entrances. Signed with HMAC-SHA256, retried with exponential backoff.

EVENTS

Idempotency, by default

Idempotency-Key headers on every write. Replays return the original response with the original log id.

RELIABILITY

Marketing-grade events

Stream conversions and entrances directly into GA4, Meta CAPI, or your own warehouse via webhooks.

ACTIVATION
Quickstart

Live in four steps, paid in five.

1

Mint a token

Exchange your client credentials for a short-lived bearer at /connect/token. Cache for ~50 minutes.

2

Discover events

Pull the event catalogue with localized names, slots, and pricing assortments. Filter by date, venue, slug.

3

Build a cart

Create an idempotent cart, add items by article id or slug, attach a customer, choose a payment provider.

4

Confirm & deliver

Lock the cart, run checkout, receive Quicodes + ticket links. Webhook fires on every successful purchase.

curl {{API_BASE_URL}}/connect/token \
  -u $CLIENT_ID:$CLIENT_SECRET \
  -d "grant_type=client_credentials&scope=Shop"

# → returns access_token

curl {{API_BASE_URL}}/shop/v1/discovery/events \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Accept-Language: de-DE"
  1. Your backend calls ADITUS:
    Token
    POST /connect/token

    Client credentials in, short-lived bearer out. Secrets never leave your backend.

  2. Your backend calls ADITUS:
    Event discovery
    GET /shop/v1/discovery/events

    Localized catalogue of events, slots, and pricing assortments.

  3. Your backend calls ADITUS:
    Cart — idempotent
    POST /shop/v1/cart

    Create the cart, add items, attach the buyer. Retries are safe — same cart, no duplicates.

  4. Your backend calls ADITUS:
    Checkout
    POST /shop/v1/cart/{id}/checkout

    Lock the cart and pay. The response carries Quicodes and ticket links for delivery.

  5. ADITUS calls your backend (asynchronous):
    Webhookasync
    POST https://your-backend/webhook

    After every successful purchase ADITUS calls your endpoint — asynchronously, independent of the checkout response.

The whole flow, end to end — four synchronous calls out, one asynchronous webhook back.
Shop Micro Frontend

The ticket shop, native on your website.

One mount() call embeds the complete purchase journey — discovery, cart, registration, checkout — directly into your page: no iframe, in your brand look via design tokens, localized and responsive out of the box.

Discover the Micro Frontend →
Experience Days event page with the embedded ticket shop showing ticket categories, article details, prices and quantity controls
API reference

All endpoints, neatly grouped.

From OAuth token to webhook replay — 10 sections, every request documented with examples, headers, and responses.

Introduction

Your starting point for the ADITUS API: what the platform covers, how the sections fit together, and where to begin your integration.

Guidelines

The API's conventions: request and URI structure, authentication via Basic or OAuth, HTTP verbs, status codes, and the shape of every response.

Just Entrance

ADITUS hardware can be used with external registration vendors. There are different ways to realise the requirements to connect external systems for a smooth visitor experience ons

Example: import external tickets, reconcile them automatically and make them ready for entry instantly.

Ticket purchase & registration

The Shop API deals with requests concerning shop processes. This includes finding shop resources, the user and managing the cart and buying process. Discovery Uses to discover the

Example: a full in-app ticket purchase — load the assortment, fill the cart, capture buyer details, pay.

Byndr

Byndr is a product API designed to enable seamless, secure connections between event attendees through badge (QR code) scans. It facilitates the creation of unidirectional, recipro

Survey

A survey is an instrument for systematic data collection. It consists of a series of questions designed to collect specific information from visitors. Main topics are: - Dynamic fo

Assets

Please prefer using this API section over the deprecated theme API. The Assets API serves static content for our products, such as images, tickets and receipts, as well as theming

In the live demo we show you, among other things, how to fetch and use the assets →

Webhooks

🚀 Connect your ticket shop with your favorite apps! Imagine your ticket shop could communicate with your CRM, accounting tools, or newsletter systems in real time — no more manual

Example: a scan at entry fires a real-time webhook — Salesforce, HubSpot & co. kick off follow-ups automatically.
View all sections →
Live-Demo

Experience the API live and hands-on.

The live demo walks you through a fully modelled fair-event with assortments, tickets, cart, and registration — each step shows the real API request and live response, no card needed.

Open live demo