Integration guide

Credentials and permissions

API secrets identify your server application. They do not identify a signed-in customer and never belong in a browser.

Send the credential from your server

Use Authorization: Bearer with an active nt_test_… or nt_live_… secret. Browser requests carrying Origin are rejected for secret-key endpoints. A public nt_widget_… identifier cannot authenticate private REST operations.

Keys expire, can be revoked or rotated, and remain bound to their application, organiser, environment and current creator permission. Application suspension or event grant removal restricts access immediately at the transactional boundary.

Authorization: Bearer YOUR_SERVER_SECRET
Content-Type: application/json

Choose the narrowest scope

events:read, tickets:read and availability:read expose assigned published catalogue information. checkout:write creates hosted sessions; orders:read returns only your application’s results and orders.

tickets:status reads purchased admission state. attendees:read exposes names; attendee email/phone additionally requires attendees:contact. sales:read, groups:read and refunds:read expose minimal attributed summaries.

entry:verify permits verification as the key creator; admission also requires entry:check-in. Both require explicit deployment opt-in and current organiser/event authority. No partner admin/refund-write, QR export or machine group-claim capability is advertised.

Limits, rotation and revocation

Base budgets are 60 requests/key/minute, 180/application and 300/organiser, with global/trusted-IP limits. Hosted creation and entry have additional conservative budgets. On 429, honour Retry-After. Limits fail closed if storage is unavailable.

Rotate a leaked key, remove it from source/logs and revoke the old key. Keep each key in one environment. No administrator receives raw credentials through the integration oversight screen.