NFC API Reference
Issue NFC devices, read balances, record scans, and take real ZMW top-ups. Every endpoint on this page is generated from the published OpenAPI contract.
Auth
API key (Bearer)
Format
JSON envelope
Rate limits
Per tier, enforced
Base URLs
This deployment serves the API at the base below. Published servers are listed in the OpenAPI document.
This deployment
https://www.tickettrails.com/api/v1
- https://api.tickettrails.comProduction
- https://sandbox-api.tickettrails.comSandbox (test keys only)
Authentication
Every endpoint requires an API key. Keys are issued from your dashboard.
Authorization: Bearer tt_live_your_api_keyDeprecated: the X-API-Key header is still accepted for backwards compatibility, but it is no longer part of the published contract. Use Authorization: Bearer.
Rate limits
Limits are enforced per API key and enforced server-side. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and Retry-After headers.
| Tier | Requests / minute | Requests / day |
|---|---|---|
| Free | 10 | 100 |
| Basic | 60 | 5,000 |
| Professional | 300 | 20,000 |
| Enterprise | 1000 | Unlimited |
{
"data": {
"id": "dev_01HZX9K2QF",
"type": "wristband",
"status": "ACTIVE",
"active": true,
"balance": { "amount": "1250.00", "currency": "ZMW" },
"lastUsedAt": "2026-08-27T14:30:00Z",
"issuedAt": "2026-06-01T09:00:00Z"
},
"error": null
}Related resources
Integration Support
Help with endpoint behaviour, authentication, and debugging.
Open support
Fees and Billing
Fee responsibility and checkout pricing behaviour.
Open fees guide
Platform API
Events, orders, payments, tickets, and analytics endpoints.
Open API portal
API Keys
Issue and rotate the keys that authenticate these requests.
Manage keys
Top-ups settle in ZMW and credit the device balance only after the payment gateway confirms.