All requests must be signed using your API Token and your private Secret Key.To start, you'll need to build your input string. Your
| Note |
|---|
Your string-to-be-signed should always include the ? query parameter delimiter regardless of whether or not there are query string parameters. |
GET
...
Requests
To start, you 'll need to build up a will need to create the string to use in computing the X-Signature string that includes the request method GET, the host name (e.g.api.ticketevolution.com), the path (e.g. /brokerages), and an optional query string that must be sorted by key (e.g. ?page=1&per_page=1).
...
Here's what that full string should look like when you put it all together:
...
| language | bash |
|---|
GET
...
api.ticketevolution.com/v9/brokerages?page=1&per_page=1
or a request without parameters
...
GET
...
api.ticketevolution.com/v9/categories?
POST, PUT, and DELETE requests
In the case of POST,PUT and DELETE requests when a request body is present, the request body should be used in the source string in lieu of the query string.
...
POST
...
api.ticketevolution.com/v9/clients?{"clients":[{"name":"Michael
...
Starr"}]}
...
Computing the
...
X-Signature
Use our X-Signature Generator to check if the signatures you're making are correct, and generate cURL requests right in the browser.
Once you 've built up have created the input string as shown above, it should be hashed using HMAC-SHA256 using the secret obtained in the Brokerage management console in the Broker Exchangeyour API Secret. Below are some examples and of how to compute X-Signature. Some examples for some additional languages can ebe may be found at http://www.jokecamp.com/blog/examples-of-creating-base64-hashes-using-hmac-sha256-in-different-languages/:
...
| Code Block | ||
|---|---|---|
| ||
curl -i \ -H Accept: application/json \ -H X-Signature: ohGcFIHF3vg75A8Kpg42LNxuQpQZJsTBKv8xnZASzu0= \ -H X-Token: abc \ -X GET 'http://api.ticketevolution.com/v9/brokerages?page=1&per_page=1' |
401 Unauthorized
If you 're having trouble and getting 401 responses back from your requestsare getting 401 Unauthorized responses, please use the X-Signature Generator to make sure you 're generating a valid signatureare correctly computing the X-Signature.