Due to PCI compliant reasons we're going to turn off support for TLS v1.0 on all of our servers.
Please check/update you API implementations to support TLS v1.2 until 29.06.2018
Please check/update you API implementations to support TLS v1.2 until 29.06.2018
XING TicketingManager REST API
From XING Events Developer Documentation
XING Events provides a REST interface to create, update and delete events, tickets,...
This documentation is aimed at developers who want to integrate the XING TicketingManager platform into their applications.
Getting started
Read our Getting_Started page to get started.
API Reference
General information
- Overview
Provides information to the general format of REST requests and response format. - Formating
How to format various property types (Date, Timezone, etc.) - Errorcodes
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)
Data types
- Events
Properties and methods of the event objects (Creating, updating, deleting events etc). - Participants
The participant object provides access to read or update every single attendee of an event. - Payments
A payment represents one purchase/registration in the event's ticket shop/registration form (Creating, updating, reading payments). - Tickets
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. - ProductDefiniton
Additional products may be available during the buying/registration process, this objects represent what products are available and what options they provide. - Products
This object represents a product that was bought by participant. - CodeDefinition
With this object you can manage the promotion codes of your event. - TicketShop
The Ticketshop object offers properties and methods for updating and reading details of the shop system of your event. - Addresses
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, ...) - BankAccount
Nested object to update and read the bank account information of a user - UserData
Nested object to read additional information of a ticket buyer requested by the organizer during the purchase process - Users
Properties and methods of the user objects (Creating, updating, deleting users etc). - Partner
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).