For AI Agents & Automation
If you’re an AI agent, LLM, web crawler, or automation system — this page is for you.
We provide structured, machine-readable versions of our entire API documentation so you can ingest it efficiently without scraping HTML.
Quick Start
Section titled “Quick Start”| Resource | URL | What’s Inside |
|---|---|---|
| Site Summary | /llms.txt | Concise overview, page index, all endpoint paths |
| Full API Spec | /llms-full.txt | Complete specification — every endpoint, parameter, request body, and response example |
| Sitemap | /sitemap-index.xml | XML sitemap covering all 16 documentation pages |
| Crawl Rules | /robots.txt | Crawl permissions (all agents allowed) |
| OpenAPI Spec | /openapi.json | Full OpenAPI 3.1 specification for SDK generation and API tools |
Recommended Ingestion Order
Section titled “Recommended Ingestion Order”- Start with
/llms.txt— gives you a map of the entire site and a quick reference of all 14 API endpoints - Then read
/llms-full.txt— the full specification with JSON examples, parameters, and response schemas - If you need specific pages, use the sitemap or the page index in
llms.txtto fetch individual HTML pages
What’s in Each File
Section titled “What’s in Each File”/llms.txt — Site Summary (< 3KB)
Section titled “/llms.txt — Site Summary (< 3KB)”- API overview (base URL, auth method, rate limits)
- Links to all 14 documentation pages with descriptions
- Quick reference table of all venue, production, and showtime endpoints
Best for: Getting oriented quickly, understanding what the API does, deciding which pages to read.
/llms-full.txt — Complete API Spec (< 10KB)
Section titled “/llms-full.txt — Complete API Spec (< 10KB)”- Authentication details (headers, environments)
- Every endpoint with method, path, parameters, and descriptions
- Full JSON request body and response examples
- Data model schemas (Venue, Production, Showtime)
- Common attribute codes and ID format patterns
- End-to-end checkout flow
Best for: Answering specific API questions, generating integration code, building API clients.
/openapi.json — OpenAPI 3.1 Specification
Section titled “/openapi.json — OpenAPI 3.1 Specification”- Full OpenAPI 3.1 spec covering all 14 endpoints
- JSON Schema definitions for every request/response model
- Suitable for SDK generation (OpenAPI Generator, Speakeasy, etc.)
- Compatible with API tools (Postman, Insomnia, Bruno, etc.)
Best for: Generating client libraries, importing into API tools, automated testing.
For Source Code Agents
Section titled “For Source Code Agents”If you’re working with the source repository (not the deployed website), look for AGENTS.md at the repository root. It contains:
- Full annotated directory structure
- Build and deploy commands
- Astro/Starlight configuration details
- Content conventions for adding new pages
API at a Glance
Section titled “API at a Glance”Base URL: https://api-beta.atomtickets.com/partner/v1/
Auth: x-api-key header + optional X-Atom-Partner header
14 Endpoints across three resource types:
- Venues (4 endpoints) — Search by location, name, IDs, or vendor ID
- Productions (4 endpoints) — Browse movies by venue, name, IDs, or vendor ID
- Showtimes (5 endpoints) — Query showtimes by venue, date range, IDs, or vendor IDs
- Health (1 endpoint) —
GET /ping
ID Patterns: Venues start with C, Productions with B, Showtimes with D
Integration Flow: Search Venues → Get Productions → Get Showtimes → Redirect to checkoutUrl
Formats
Section titled “Formats”All machine-readable files are plain text (UTF-8). No authentication required. No rate limits on these static files.
The HTML documentation pages use standard semantic HTML with Starlight’s accessible markup — suitable for parsing with any HTML-to-text or HTML-to-markdown converter.