An API key lets a system you run — a website, a CRM, an automation tool — read your organizer’s events through the TixFix API without sharing a login. Keys live in Settings → API Keys.
Screenshot coming soon. This flow needs a live order or a device we could not reach when these docs were captured. The steps below are written from the product as it behaves today; the illustration will follow.

Who can manage keys

The organizer’s owner and Admin team members see the API Keys tab. Scanner Plus members do not. TixFix staff cannot create, view or remove your keys either: the tab is closed to them even when they are helping with your account.

Create a key

1

Open Settings → API Keys

Click Settings in the left sidebar, then the API Keys tab.
2

Click Create API key

Enter a Name of up to 40 characters. Name the key after the system that will use it, such as Zapier or Website, so you know what to revoke later. Click Create.
3

Copy the key

The Copy your API key dialog shows the full key, starting with tix-. Click the copy button and paste the key into the other system’s configuration, then click Done.
The full key is shown once. After you close the dialog it cannot be shown again; if you lose it, delete that key and create a new one.
Each key then appears in the list with its name, who created it, a masked form of the key (its start and last four characters, such as tix-g2986O…c0J8), the date it was created, when it was last used, and its status.

The two-key limit

Each organizer can hold two keys. A revoked key still counts until you delete it, so when Create API key is disabled, delete a key you no longer use. Two keys let you rotate without downtime: create the new key, switch the other system over to it, then delete the old one.

Revoke or delete a key

Both actions ask you to confirm first, and both take effect immediately. Revoke when you want the list to keep a record of the key; delete when you need the slot back.

Keep keys safe

  • Store a key in server-side configuration, never in browser code, mobile apps or public repositories.
  • Use a separate key per system so you can revoke one without touching the other.
  • Each key’s Last used date shows when it last made a request, refreshed at most every few minutes. A key that has not been used in months is a good candidate to delete.
Still stuck? Email contact@tixfix.ai with your event name and a screenshot.