How to Create and Use an API Token
API tokens let another system connect to your TicketingHub account. You must have admin access to manage them.
What Can I Use an API Token For?
- Send TicketingHub data to reporting software or a data warehouse.
- Let a custom partner platform read products and prices.
- Build a server-side booking experience that checks live availability.
An API token does not create a built-in Google Sheets connection. See How to Export TicketingHub Data and Connect Other Tools to choose between CSV exports, Zapier, webhooks, and API access.
Enable API access
- Go to Settings → Features.
- Turn on Api access.
This is a self-service setting. After you enable it, API Tokens appears in Settings.
Create a token
- Go to Settings → API Tokens.
- Select Generate API token.
- Enter a name that identifies the system using the token.
- Choose Supplier API (V2) for supplier management, Widget API for availability and booking, or OCTO API for connecting systems that speak the OCTO standard.
- If you chose Supplier API (V2) or OCTO API, you can select Read-only when the integration only needs to view data. This option does not apply to Widget API tokens.
- Add an expiry date if needed, then generate the token.
- Copy the token immediately and store it securely. The full token is shown only once.
Use the token
Send the token in the Authorization header of each API request:
Authorization: Bearer YOUR_TOKENUse API tokens only in secure server-side systems. Do not put a token in website code, emails, chat messages, or shared documents.
Revoke a token
Go to Settings → API Tokens and select Revoke next to the token. Revocation takes effect immediately, so the connected system will stop working until it uses a replacement token.
Create a separate token for each integration, use only the access it needs, and revoke tokens that are no longer in use. For event-based updates, you may prefer webhooks or the Zapier integration.