The Exchange API enables developers to write their own tools to search existing ticketpplic inventory, manage their own inventory, and create ordersOur Exchange API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON request bodies, returns JSON-encoded responses, and uses standard HTTP response codes and verbs.
Authentication
Authentication is based on API Tokens plus a shared secret which is used to compute a required X-Signature header.
Credential Type | Description |
|---|---|
Upload Credential | Used only to upload inventory either via the Auto Uploader software or via a special API endpoint. |
API Credential | The typical credential which acts on behalf of a Brokerage. |
User Credential | A User Credential is used to act on behalf of a specific User and is need for certain endpoints. |
Environments
There are two distinct environments available for the API. The Production environment is the one your production applications should use, but a Sandbox environment is also provided for testing your integrations. The Sandbox is an environment completely isolated from Production, but has the same Events, Performers, Venues, and Configurations as the Production environment.
| Child pages (Children Display) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Mailing List
Our low-volume mailing list for developers who are integrating with the TEvo API will keep you informed of changes, additions, and improvements to our APIs. Sign up at http://eepurl.com/ghzUOz .
...