Developer documentation

The REST API and MCP server let buyers and organizers read their own tickets and orders; organizers can also manage events, ticket tiers, attendees, check-in, and refunds. They are free on every plan.

Get an API key

Active accounts can create keys from the Account page → API Access. A key is shown once; choose scopes, set an optional expiry, and revoke it there. High-risk scopes are unchecked by default.

Personal ticket access

The tickets:read scope reads your own tickets and orders. Purchase statuses are active (2), cancelled under the Refund Guarantee (8), or refunded by the organizer (9); cancelled_at is present only for status 8. Refund amounts come from the latest status-2 refund log. The optional high-risk tickets:codes scope adds ticket codes and eligible online or recording links. These scopes do not allow purchases, refunds, or Guarantee cancellations.

Authentication

Send the key in the Bearer authorization header.

curl -H "Authorization: Bearer tp_YOUR_API_KEY" https://www.ticketplace.vip/api/v1/account

Base URL: https://www.ticketplace.vip/api/v1

Scopes

ScopeAccessAccountEnabled by default
tickets:readRead my tickets and ordersActive accountYes
tickets:codesTicket codes and join linksActive accountNo
events:readRead organizer account and eventsOrganizerYes
events:writeCreate and edit eventsOrganizerYes
attendees:readRead attendees and ordersOrganizerYes
checkin:writeRedeem ticketsOrganizerYes
payments:writeRefund ordersOrganizerNo
deleteDelete photos or deactivate eventsOrganizerNo

Safety and limits

Pagination and errors

List endpoints use limit and cursor where documented. Responses include next_cursor when another page is available. Errors use an error object; validation details may also be returned in errors.

{
  "error": {
    "code": "validation_error",
    "message": "The request could not be processed."
  },
  "errors": { "name": "This field is required." }
}

REST endpoint reference

Generated from the current OpenAPI document at request time. See OpenAPI 3.1 JSON.

Account

MethodPathSummaryScope
GET/accountGet the authenticated organizer profileevents:read

Personal tickets

MethodPathSummaryScope
GET/meGet the authenticated account and API key scopestickets:read
GET/me/ticketsList the authenticated account's own ticket purchasestickets:read
GET/me/tickets/{purchase_id}Get one of the authenticated account's own ticket purchasestickets:read

Events

MethodPathSummaryScope
GET/eventsList the authenticated organizer's eventsevents:read
POST/eventsCreate a complete draft eventevents:write
GET/events/{event_id}Get an organizer-owned eventevents:read
PATCH/events/{event_id}Update editable event detailsevents:write
POST/events/{event_id}/deactivatePreview or deactivate an eventevents:write + delete
POST/events/{event_id}/photosUpload an event photoevents:write
DELETE/events/{event_id}/photos/{photo_id}Preview or delete an event photoevents:write + delete
POST/events/{event_id}/publishPreview or publish an eventevents:write
PATCH/events/{event_id}/tiers/{tier_id}Update ticket tier details and priceevents:write
GET/events/{event_id}/videosList an event's videosevents:read
POST/events/{event_id}/videosAdd a YouTube or Vimeo videoevents:write
DELETE/events/{event_id}/videos/{video_id}Preview or delete an event videoevents:write

Attendees

MethodPathSummaryScope
GET/events/{event_id}/attendeesList attendees for an owned eventattendees:read

Orders

MethodPathSummaryScope
POST/check-inRedeem a ticketcheckin:write
GET/orders/{purchase_id}Get an organizer-owned orderattendees:read
POST/orders/{purchase_id}/refundPreview or refund an orderpayments:write

Connect your AI tool (MCP)

MCP URL: https://www.ticketplace.vip/mcp

Most AI tools connect by signing in: add the URL, sign in to Ticket Place when asked, and choose the permissions. High-risk permissions start unchecked, and no API key is needed. You can revoke a connection at any time under Account → API Access → Connected apps.

Once connected, name Ticket Place in your request so the AI uses it instead of searching the web, for example: Use Ticket Place to list my upcoming events. Do not search the web.

ChatGPT, ChatGPT Work and dots

  1. On the ChatGPT website (not the mobile app), open chatgpt.com/plugins.
  2. Click +, then Add custom MCP server.
  3. Name: Ticket Place. Server URL: https://www.ticketplace.vip/mcp. Authentication: OAuth. Leave the client ID and secret empty.
  4. Select I understand and want to continue, then Create as a plugin.
  5. Install the plugin, sign in to Ticket Place and approve access.
  6. In a chat, type @ and choose Ticket Place.

When new tools are added, refresh the plugin in its settings. Details: OpenAI custom MCP server guide.

Dots: your ChatGPT dots use the same plugin. Once it is installed in the ChatGPT Plugins tab, your dot can use it within the permissions you approved; there is nothing extra to set up. See Dots FAQ.

Claude (claude.ai, Claude Desktop, Cowork and mobile)

  1. Open Customize → Connectors and click Add.
  2. Hover over Custom and select Web.
  3. Name: Ticket Place. Remote MCP server URL: https://www.ticketplace.vip/mcp. Click Continue.
  4. Authentication: Sign in now. OAuth client: Register automatically.
  5. Click Add, then sign in to Ticket Place and approve access.

A connector added once works in every Claude app. The Free plan allows one custom connector; on Team and Enterprise an owner adds it first. Details: Claude custom connectors.

Grok

  1. Open grok.com/connectors.
  2. Click New Connector, then select Custom.
  3. Enter the MCP server URL https://www.ticketplace.vip/mcp, then sign in to Ticket Place and approve access.

On Grok Business and Enterprise, a team admin first adds the server in the xAI console under Grok Business → Connectors → Add Connector → Other; then each member connects on grok.com/connectors. Details: Grok connectors.

Claude Code

claude mcp add --transport http ticket-place https://www.ticketplace.vip/mcp

Then run /mcp in Claude Code, select ticket-place and choose Authenticate. Add --scope user to use it in every project. Details: Claude Code MCP documentation.

Codex (CLI, IDE extension and ChatGPT desktop app)

codex mcp add ticket-place --url https://www.ticketplace.vip/mcp
codex mcp login ticket-place

The login command opens your browser to sign in. The Codex CLI, IDE extension and ChatGPT desktop app share this setup in ~/.codex/config.toml. Details: Codex MCP documentation.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
   "mcpServers" : {
      "ticket-place" : {
         "url" : "https://www.ticketplace.vip/mcp"
      }
   }
}

Restart Cursor, then sign in to Ticket Place when Cursor asks to connect the server. Details: Cursor MCP documentation.

VS Code (GitHub Copilot)

  1. Run Chat: Open Customizations and select MCP Servers.
  2. Click Add Server (+), choose HTTP and enter https://www.ticketplace.vip/mcp.
  3. Enter the server ID ticket-place, select Global → Copilot Global, and complete the sign-in.

Or add it to ~/.copilot/mcp-config.json:

{
   "mcpServers" : {
      "ticket-place" : {
         "tools" : [
            "*"
         ],
         "type" : "http",
         "url" : "https://www.ticketplace.vip/mcp"
      }
   }
}

Details: VS Code MCP servers.

Devin

In the Devin web app, open Customize → MCPs and add a custom MCP server with transport HTTP, server URL https://www.ticketplace.vip/mcp, authentication OAuth and access Personal. Save it, then click Connect and sign in. For the Devin CLI:

devin mcp add ticket-place --url https://www.ticketplace.vip/mcp
devin mcp login ticket-place

Details: Devin MCP documentation.

Meta Muse

Muse has no settings form for MCP servers. Paste this message into a Muse chat and approve the sign-in it shows you:

Create a Custom Connector for a remote MCP server and connect to it:
- Name: Ticket Place
- Transport: remote streamable HTTP
- URL: https://www.ticketplace.vip/mcp
- Auth: OAuth (sign in when prompted; there is no API key to paste)
Then list its tools to confirm the connection works, and save it as a reusable skill.

Other MCP clients

Use Streamable HTTP at https://www.ticketplace.vip/mcp. The server supports OAuth 2.1 with discovery at /.well-known/oauth-protected-resource and dynamic client registration. Tools without OAuth can send an API key from Account → API Access as a bearer token, for example:

claude mcp add --transport http ticket-place https://www.ticketplace.vip/mcp --header "Authorization: Bearer tp_YOUR_API_KEY"

For clients that only run local (stdio) servers, use the mcp-remote bridge:

{
   "mcpServers" : {
      "ticket-place" : {
         "args" : [
            "-y",
            "mcp-remote",
            "https://www.ticketplace.vip/mcp",
            "--header",
            "Authorization: Bearer tp_YOUR_API_KEY"
         ],
         "command" : "npx"
      }
   }
}

Available tools: get_account, list_events, get_event, create_event_draft, update_event, update_ticket_tier, upload_event_photo, delete_event_photo, list_event_videos, add_event_video, delete_event_video, publish_event, deactivate_event, list_attendees, get_order, check_in_ticket, refund_order.