Our 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.
...
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.
Environment | API URL |
|---|---|
Sandbox | https://api.sandbox.ticketevolution.com |
Production | https://api.ticketevolution.com |
For more information on placing test orders in Sandbox see Placing Test Orders.
...
Most endpoints that accept date parameters such as updated_at or occurs_at support the following conditionals for creating a date range. The deleted endpoints utilize deleted_at.
.eq- equal (case-sensitive).not_eq- not equal (case-sensitive).gt- greater than.gte- greater than or equal.lt- less than.lte- less than or equal
...
Our low-volume mailing list for developers who are integrating with the TEvo Exchange API will keep you informed of changes, additions, and improvements to our APIs. Sign up at http://eepurl.com/ghzUOz .