Please check/update you API implementations to support TLS v1.2 until 29.06.2018
XING TicketingManager REST API
XING Events provides a REST interface to create, update and delete users and events. Nearly any computer language can be used to communicate over HTTP with the REST server.
This documentation is aimed at developers who want to integrate the XING TicketingManager platform into their applications.
- First, you have to create an account at XING Events if you do not have one yet.
- After creating your account, you have to register your project to get access to an API key (See How to get your API key for details).
- Using your API key, you can start to make REST calls. See the documentation below for details. If you need help, take a look at the How-Tos.
Provides information to the general format of REST requests and response format.
How to format various property types (Date, Timezone, etc.)
A list of all error codes generated by the REST API.
- Data Synchronization v2
Documentation of the data synchronization API (Used for informing you about new objects or updates of your object)
Properties and methods of the event objects (Creating, updating, deleting events etc).
The participant object provides access to read or update every single attendee of an event.
A payment represents one purchase/registration in the event's ticket shop/registration form (Creating, updating, reading payments).
During one purchase/registration the buyer may buy one or multiple tickets (Reading of ticket details).
- Ticket Categories
Properties and methods of the selected/available ticket categories objects.
Additional products may be available during the buying/registration process, this objects represent what products are available and what options they provide.
This object represents a product that was bought by participant.
With this object you can manage the promotion codes of your event.
The Ticketshop object offers properties and methods for updating and reading details of the shop system of your event.
The address object is used in multiple cases to read or update a specific address (billing address, shipment address or other address requested in the ticket shop).
- Ticket Types
Nested object to update and read the available types of tickets in the shop (e.g. E-Ticket, Paper-Ticket, ...)
- Payment Types
Nested object to update and read the available payment types in the shop (e.g. Credit card, PayPal, ...)
Nested object to update and read the bank account information of a user
Nested object to read additional information of a ticket buyer requested by the organizer during the purchase process
Properties and methods of the user objects (Creating, updating, deleting users etc).
Properties and methods of the partner objects (Creating, updating, deleting partners etc).
- API Key
Properties and methods of the api key objects (Creating, updating API keys etc).