Skip to main content
Ticket Tool
Documentation

Authentication

Learn how to authenticate your API requests using API tokens. The base URL is https://api.ticket-tool.app/v1.

Available on Pro and higher

API access is included on the Pro plan and higher (Pro, Team, and Enterprise). It is not available on the Free or Community plans.

Creating an API token

Create tokens in the dashboard:

Single server

Open the Integrations page in the server dashboard and use the API tab.

Organization

Open Organization Settings.

When you create a token, you can:

Name the token

Give it a name so you can identify it later.

Select scopes

Select the scopes it is allowed to use (for example tickets:read, tickets:write, or org:analytics:read).

Set an expiry (optional)

Set an optional expiry date, or leave it with no expiry.

Copy it once

The token value is shown only once at creation time, so copy it and store it somewhere safe right away. The dashboard keeps a short prefix and the token's metadata, but it cannot show you the full value again.

Using a token in requests

Tokens look like tt_... and are sent in the Authorization header as a Bearer token:

Authorization: Bearer tt_...

A guild token is bound to one server, so resource paths are direct (GET /v1/tickets). An organization token reaches any member server by prefixing a guild path with /org/servers/{guildId} (for example GET /v1/org/servers/{guildId}/tickets) and has cross-server reporting under /v1/org.

Token limits per plan

The number of active tokens you can hold depends on your plan:

10
Pro
Active tokens
10
Team
Active tokens
Unlimited
Enterprise
Active tokens

Managing and revoking tokens

You can view your active tokens and revoke any token at any time from the same place you created it. Revoking a token takes effect immediately, so generate a replacement before retiring one that is still in use.

Next steps