From API to a finished experience.

Ticket sales inside your own event app

Want to sell tickets in your own event app? No problem. Every feature of the ADITUS ticket shop is available directly in your app through the matching API. A sale or a voucher redemption can be integrated with little effort.

You decide how many of the API's functions you use and which ones you handle yourself. Our Discovery Assortment endpoint returns the complete list of sellable products including prices, images and descriptions, fully localized, of course. From there it is only a few steps to checkout: use the payment providers configured in the ADITUS system, or handle payment yourself.

1. 1

   Load the assortment

   The Discovery Assortment endpoint returns every sellable product including prices, images and descriptions. Everything fully localized.

2. 2

   Select & cart

   Your users pick tickets right in the app, and the cart is assembled in just a few steps.

3. 3

   Buyer details

   Fast entry of buyer details: you decide which fields you collect.

4. 4

   Payment

   Use the payment providers configured in ADITUS, or handle payment yourself.

Import external tickets seamlessly

Need to import external tickets? Our API takes care of it. No matter which registration system you use: with our import endpoints you pull external tickets and attendee data seamlessly into the ADITUS system.

No duplicate headaches: you don't have to check what's already there yourself. Our API recognizes existing tickets, updates them live and adds new ones. And the moment the data lands in the system, the tickets are immediately valid for entry; features like badge printing at the door work without any delay.

1. 1

   Import tickets

   Hand over external tickets and attendee data through our import endpoints, no matter which registration system they come from.

2. 2

   Automatic reconciliation

   No duplicate headaches: the API recognizes existing tickets, updates them live and creates new ones.

3. 3

   Instantly ready for entry

   After the import the tickets are immediately valid for entry. Badge printing and more work without delay.

Import booth registrations, auto-assign free allowances

Importing exhibitor booth registrations, including free allowances for exhibitor badges and vouchers, is fundamental to trade-fair ticketing. That's why we provide a standardized, highly flexible import interface.

You can drive it directly, or we connect your ERP, exhibitor shop or booth-booking system (such as SAP, Salesforce or Rubin) through our integration platform for fully automated imports. And to make handling as effortless as possible for your exhibitors, we ensure a seamless transition from your exhibitor shop into our Exhibitor Service Center (ESC).

1. 1

   Standard import interface

   Hand over booth registrations through our standardized, highly flexible import interface, manually or fully automated.

2. 2

   Auto-assign allowances

   Exhibitor badges and vouchers are allocated automatically in the right quantity, based on each registration.

3. 3

   Seamless into the ESC

   The handover from your exhibitor shop into the Exhibitor Service Center is seamless. Exhibitors manage everything in self-service.

Sales as they happen, in the dashboard you already have.

Your data team owns a warehouse and a pipeline. Business Intelligence is the outbound ADITUS API for exactly that: it answers from live data, hands over the rows, and the modelling stays with you.

Four datasets over standard OData v4 (tickets, scans, statistics groups and surveys), pulled page by page with a keyset walk into the tables you already have.

1. 1

   Get a token

   Client credentials against the token endpoint, scope ticketinghub-api. The secret never leaves your server.

2. 2

   Read the schema

   One GET on $metadata returns all four datasets with 500 columns, generated by the running instance and not typed off a PDF.

3. 3

   Walk the pages

   $select the columns you need, $orderby the key, $filter rows greater than the last key, $top for the page size. The last page costs what the first one did.

4. 4

   Land it in the warehouse

   Rows go into your staging tables as they are; modelling, metrics and history stay yours. Power BI, Tableau, ADF or Fivetran read the same endpoint without custom code.

Result: everything your ticketing knows lands in your staging tables in one pass. There is no export job and no snapshot in between: every run reads the current state, and the walk continues from the last key. Run it as often as your dashboard needs, and a ticket sold a minute ago is already in the rows.

How many people actually came, which campaign sold, what each exhibitor did with their allocation: the questions are yours, the data is already there.