Every request carries an organizer API key in the Authorization header:
A key is tix- followed by 43 random characters (letters, digits, - and _). It belongs to one organizer and reads only that organizer’s data; there is nothing to pass to say which organizer you mean. The scheme is case-sensitive: write Bearer exactly, followed by one space.

Managing keys

Keys are created, revoked and deleted in the organizer dashboard under Settings → API Keys by the organizer’s owner or an Admin team member. Each organizer can hold two keys at a time. The full key is shown once, at creation; afterwards the dashboard shows only its start and last four characters. See API keys for the walkthrough.
Treat a key like a password. Keep it in server-side configuration, never in browser code, mobile apps or public repositories. If a key leaks, revoke it in Settings → API Keys and create a new one.

What a rejected request looks like

All 401 cases return the same message on purpose, so a response never reveals whether a key once existed. Each answers with the error body.