GoFastTickets Developer Resources and Public API v1

The GoFastTickets Public API v1 lets authorised resellers automate their own event catalogue, listings, ticket delivery, sales, and account statistics.

When to use the GoFastTickets API

Use the API when an authenticated GoFastTickets reseller needs to search publishable events, create or update listings, publish or unpublish inventory, duplicate listings, obtain payment links, upload sold tickets, or retrieve sales and dashboard statistics. Consumer ticket discovery should use the public website; the API is account-bound and is not a general event-data feed.

Every protected request uses an API key issued for one reseller account. Send it as Authorization: Bearer GFT_API_KEY. Never place a key in a URL, browser bundle, prompt, public repository, or log. Integrations should follow the OpenAPI 3.1 contract, respect scopes and rate limits, preserve X-Request-Id for support, and require explicit user confirmation before any purchase, publish, unpublish, delivery, or deletion action.

Endpoints and authentication

The production base URL is https://www.gofasttickets.com/api/v1. Human-readable documentation is available at /api/v1/docs and the machine-readable OpenAPI document is at /api/v1/openapi.json. Keys are created and revoked by an authorised account operator; there is no anonymous key-creation endpoint. Responses use JSON UTF-8 except multipart ticket uploads and include stable HTTP status codes, X-Request-Id, X-API-Version, and standard RateLimit headers. Errors include code, message, resolution_hint, and request_id.

CLI and MCP

The prepared official GoFastTickets CLI package is named gofasttickets-cli and its command is gofasttickets. PyPI publication is pending. It reads GFT_API_KEY and emits machine-readable JSON. GoFastTickets does not currently publish an official MCP server; agents should use the versioned OpenAPI contract or official CLI.

Resources