Skip to main content
note

Have you noticed an issue with our API? Please email api@tickettailor.com.

Whether it's your first event ever, or your biggest event yet, Ticket Tailor makes it simple to sell tickets online.

Getting started

Conventions

  • The production API is found at: https://api.tickettailor.com.

  • All API requests are made via HTTPS. Only TLSv1.2 and higher are supported.

  • All data in a response is JSON.

  • Clients should include the header - Accept: application/json in their requests.

  • Currencies are represented by their [ISO 4217] Currency code (https://www.xe.com/iso4217.php).

  • Currency values are always in cents (or equivalent), with no decimals.

Sign up

If you haven't already, create a Ticket Tailor account. When prompted, fill out details to create a box office. Api keys are associated to the box office, meaning an api key can only access data from the box office that issued it.

Authentication

The Ticket Tailor API uses API key to authenticate requests. You can manage your API keys in your box office settings. Authentication to the API is performed via HTTP Basic Auth.

When manually adding the API key to the Authorization header, ensure it is Base64 encoded in the format: Authorization: Basic Base64Encode(api_key).

curl -X GET https://api.tickettailor.com/v1/orders \
-H 'Accept: application/json' \
-H 'Authorization: Basic c2tfMTAwMF8xMDAwX1ZHbGphMlYwVkdGcGJHOXk='

Pagination

Endpoints which enumerate objects support cursor-based (eg. or_1234) pagination via the starting_after and ending_before parameters. Both parameters take an existing value and return objects in reverse chronological order. If both parameters are provided, only ending_before is used.

Request Arguments
ending_before
optional
Returns objects listed before the named object
starting_after
optional
Returns objects listed after the named object
limit
optional
Limits the number of results per-page.
Maximum: 100

Rate limiting

You can make up to 5000 requests per 30 minutes to the API To see your current rate limit status, check the HTTP headers returned by any API request. If you’re running into this error frequently, or think you need a higher rate limit, drop us a line at hi@tickettailor.com.

HeaderName
X-Rate-Limit-LimitThe maximum number of requests that the consumer is permitted to make per hour.
X-Rate-Limit-RemainingThe number of requests remaining in the current rate limit window.
X-Rate-Limit-ResetThe number of seconds left in the current period.
Retry-AfterThe number of seconds to wait until the rate limit window resets. This is only sent when the rate limit is reached.

Errors

status: integer
error_code: string
message: string

The Ticket Tailor API returns conventional HTTP response codes to indicate the success or failure of an API request. For errors, the response will include additional information about what went wrong, encoded in the response as JSON.

StatusError codeMessage
400Bad RequestThe request was invalid, often due to a missing a required parameter.
401UnauthorizedYour request was not authenticated correctly.
403ForbiddenYou do not have permission to perform the request.
404Not FoundThe requested resource does not exist.
422Validation errorA validation error occurred.
429Too Many RequestsToo many requests hit the API too quickly.
50XInternal Server ErrorAn error occurred on Ticket Tailor's end with our API.