Difference between revisions of "XING TicketingManager REST API"

From XING Events Developer Documentation
(Redirected page to REST API)
Line 1: Line 1:
XING Events provides a [http://en.wikipedia.org/wiki/Representational_State_Transfer 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|Getting Started]] page to get started.
==API Reference==
=====General information=====
*[[REST_API_Overview|Overview]]<br>Provides information to the general format of REST requests and response format.
*[[REST_API_Formats|Formating]]<br>How to format various property types (Date, Timezone, etc.)
*[[REST_API_ErrorCodes|Errorcodes]]<br>A list of all error codes generated by the REST API.
*[[REST_API_DataSync_v2|Data Synchronization v2]]<br>Documentation of the data synchronization API (Used for informing you about new objects or updates of your object)
=====Data types=====
*[[REST_API_Events|Events]]<br>Properties and methods of the event objects (Creating, updating, deleting events etc).
*[[REST_API_Participants|Participants]]<br>The participant object provides access to read or update every single attendee of an event.
*[[REST_API_Payments|Payments]]<br> A payment represents one purchase/registration in the event's ticket shop/registration form (Creating, updating, reading payments).
*[[REST_API_Tickets|Tickets]]<br>During one purchase/registration the buyer may buy one or multiple tickets (Reading of ticket details).
*[[REST_API_TicketCategories|Ticket Categories]]<br>Properties and methods of the selected/available ticket categories objects.
*[[REST_API_ProductDefinition|ProductDefiniton]]<br>Additional products may be available during the buying/registration process, this objects represent what products are available and what options they provide.
*[[REST_API_Products|Products]]<br>This object represents a product that was bought by participant.
*[[REST_API_CodeDefinition|CodeDefinition]]<br>With this object you can manage the promotion codes of your event.
*[[REST_API_TicketShops|TicketShop]]<br>The Ticketshop object offers properties and methods for updating and reading details of the shop system of your event.
*[[REST_API_Addresses|Addresses]]<br>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).
*[[REST_API_TicketTypes|Ticket Types]]<br>Nested object to update and read the available types of tickets in the shop (e.g. E-Ticket, Paper-Ticket, ...)
*[[REST_API_PaymentTypes|Payment Types]]<br>Nested object to update and read the available payment types in the shop (e.g. Credit card, PayPal, ...)
*[[REST_API_BankAccounts|BankAccount]]<br>Nested object to update and read the bank account information of a user
*[[REST_API_UserData|UserData]]<br>Nested object to read additional information of a ticket buyer requested by the organizer during the purchase process
*[[REST_API_Users|Users]]<br>Properties and methods of the user objects (Creating, updating, deleting users etc).
*[[REST_API_ApiKey|API Key]]<br>Properties and methods of the api key objects (Creating, updating API keys etc).

Latest revision as of 13:24, 14 June 2019

Redirect to: