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

610

Endpoints

Sections

1B+

REQ/YEAR

●POST /connect/token · GET /shop/v1/discovery/events

curl https://aditus.dev/Demo_API/api/connect/token \
  -u $CLIENT_ID:$CLIENT_SECRET \
  -d "grant_type=client_credentials&scope=Shop"

# → returns access_token

curl https://aditus.dev/Demo_API/api/shop/v1/discovery/events \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Accept-Language: de-DE"

Demo system

Live status

Live check in browser

The public ADITUS demo system powers all interactive examples in this portal — event discovery, carts, checkout, and tickets run against a real Shop API with live data.

As soon as this page loads in your browser, the current availability of the Shop API, its upstream services, and the response time are checked live.

Live check runs on page load

Trusted & integrated by

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

Portrait of Marc Luzoff, CEO of ADITUS — **Marc Luzoff**CEO

Quickstart

Live in four steps, paid in five.

Mint a token

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

Discover events

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

Build a cart

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

Confirm & deliver

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

curl https://aditus.dev/Demo_API/api/connect/token \
  -u $CLIENT_ID:$CLIENT_SECRET \
  -d "grant_type=client_credentials&scope=Shop"

# → returns access_token

curl https://aditus.dev/Demo_API/api/shop/v1/discovery/events \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Accept-Language: de-DE"

Your backend calls ADITUS:
Token
POST /connect/token
Client credentials in, short-lived bearer out. Secrets never leave your backend.
Your backend calls ADITUS:
Event discovery
GET /shop/v1/discovery/events
Localized catalogue of events, slots, and pricing assortments.
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.
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.
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.

Portrait of Sebastian Kluge, Head of Products at ADITUS — **Sebastian Kluge**Head of Products

Shop Micro Frontend

The ticket shop that feels like your website.

Your visitors browse, pick their tickets and complete the purchase without ever leaving your website — integrated with just a few lines of code. Design tokens carry your brand look into every step, responsive and localized out of the box. The result: a consistent brand experience, more trust, fewer abandoned purchases — and ticket sales that simply work.

More about the Micro Frontend →

Experience Days event page with the embedded ticket shop showing ticket categories, article details, prices and quantity controls

Built for your stack

Open integration

Light DOM — no iframe, no Shadow DOM
React 18 and 19
Framework-agnostic via mount(container, config)
Semantic CSS hooks and design tokens
Live language and culture changes

Secure operation

Documented session and authentication model
Server-to-server session token minting
Concrete Content Security Policy requirements
Payment Page architecture reduces PCI scope

Production ready

Payment redirects with safe journey resume
Host callbacks and server-side webhooks
Optional GA4 ecommerce events
Compatible with SSR hosts such as Next.js and Nuxt
Source package or versioned self-hosted bundle

Portrait of Marc Ehbrecht, Team Lead Integration & Consulting at ADITUS — **Marc Ehbrecht**Team Lead Integration & Consulting

API reference

All endpoints, neatly grouped.

From OAuth token to webhook replay — 11 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 OAuth 2.0 (client credentials), 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 …

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

Just Entrance: use case →

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.

Ticket purchase & registration: use case →

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 …

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 …

Assets

The Assets API serves the platform's static content: images and icons, ticket PDFs and receipts, plus theme data such as logos, banners and colors, resolved per context.

The live demo shows how to fetch and use assets.

Open live demo →

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.

Webhooks: use case →

Business Intelligence

A read-only OData v4 feed that hands you your complete ticketing history as four analysis-ready datasets, built to bulk-load into your own data warehouse. Standard OData v4 over …

Example: your extract reads sales and scans from live data into your warehouse over OData v4 — in the dashboard while the show is on.

Business Intelligence: use case →

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