Learn TicketsX faster
Setup guides, the full command reference, Premium features, and the REST API in one place.
API Reference
The TicketsX REST API lets you integrate external tools with your server’s ticket system. Create, close, and manage tickets programmatically without the Discord UI, search your entire transcript archive, and pull the full text or HTML of any closed ticket.
The REST API is a Premium feature. API tokens can only be created and used while the server has an active Premium subscription (see the pricing page). Requests from a server without Premium are rejected with 402 and a premium_required: true field. If Premium lapses, your existing tokens are kept but stop working until you reactivate — you can still list, disable, and revoke them from the dashboard at any time.
https://api.ticketsx.xyzEvery request requires an API token passed as a Bearer token in the Authorization header. Tokens are scoped to a single guild and can be restricted per action.
Authorization: Bearer <API_TOKEN>Replace <guild_id> with your Discord server ID and <ticket_id> with the target ticket’s ID in all endpoint paths below.
Content-Type: application/json is required for all POST request bodies. 4xx responses include a JSON error field; 401 means the token is invalid, expired, or revoked; 402 means the server does not have Premium (the response also carries premium_required: true); 403 means the token is disabled or lacks the required permission; 429 means a rate limit was hit (see Rate Limits & Safety) and includes a retry_after value in seconds.