Build on the Event Platform API
30 authenticated operations across 9 resources, from event discovery through to NFC tap-to-pay. Every request is rate limited by key and logged for audit.
- Format
- JSON envelope
- Auth
- API key
- Base URL
- https://www.tickettrails.com/api/v1
const response = await fetch('https://www.tickettrails.com/api/v1/events', {
headers: {
Authorization: 'Bearer tt_live_your_api_key',
Accept: 'application/json'
}
});
if (!response.ok) {
throw new Error(`Events failed: ${response.status}`);
}
const { data, pagination } = await response.json();API surface
Generated from the published OpenAPI contract, so this list always matches what the API actually serves.
Account
22 paths
/v1/account
Analytics
22 paths
/v1/analytics/events
Events
75 paths
/v1/events
Health
22 paths
/health
NFC
55 paths · supports idempotent writes
/v1/nfc/devices
Orders
32 paths · supports idempotent writes
/v1/orders
Payments
22 paths · supports idempotent writes
/v1/payments
Tickets
44 paths · supports idempotent writes
/v1/orders/:id/tickets
Webhooks
32 paths
/v1/webhook-endpoints
Operations that move money or issue tickets require an Idempotency-Key header. Replaying a key returns the original response instead of charging twice.
Transparent API Pricing
Choose the plan that fits your needs. Every plan includes the full documentation set and community support.
Need a custom plan or higher volume? Talk to our sales team.
Getting started
Three steps from a blank project to your first authenticated response.
- 01
Create a developer account
Register a TicketTrails account to unlock API access and the dashboard.
Register - 02
Issue an API key
Generate a key from your dashboard and send it as an Authorization: Bearer header.
Manage API Keys - 03
Ship your first request
Follow the reference and the OpenAPI contract to go live.
Read the NFC reference
Ready to integrate?
Create an account, issue a key, and make your first request in minutes.