Authentication

All API requests require authentication via HTTP headers.

Required Headers

Header	Value	Required
x-api-key	API key provided by Atom Tickets	Yes
X-Atom-Partner	Agreed upon value per partner for specific use cases	No

Using Your API Key

Include the x-api-key header in every request:

curl -X GET \
  'https://api-beta.atomtickets.com/partner/ping' \
  -H 'x-api-key: YOUR_API_KEY'

Partner Header

Some endpoints may require the X-Atom-Partner header for partner-specific behavior. This value is agreed upon during your onboarding process with Atom Tickets.

curl -X GET \
  'https://api-beta.atomtickets.com/partner/v1/showtime/details/byVenue/C0057070265?isoStartDate=2024-01-15T07:00:00Z&isoEndDate=2024-01-16T07:00:00Z' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'X-Atom-Partner: YOUR_PARTNER_ID'

POST Requests

For POST endpoints, also include the Content-Type header:

curl -X POST \
  https://api-beta.atomtickets.com/partner/v1/venue/details/byIds \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY' \
  -d '{"ids": ["C0057070265"]}'

Verifying Your Setup

Use the Ping endpoint to verify your API key is working:

curl -X GET \
  'https://api-beta.atomtickets.com/partner/ping' \
  -H 'x-api-key: YOUR_API_KEY'

A successful response returns HTTP 200 with no body.