Muzeek Events API

A REST API for reading and managing events in your Muzeek account from any server-side application.

The Events API is the first REST resource. Bookings, contacts, invoices, settlements, and ticket sales are available today through MCP. Additional REST APIs for bookings, venues, tours, and settlements will be published here as they become available. If you have a use case that isn't covered yet, we'd love to hear from you.

Base URL

All endpoints are served from:

https://muzeek.ai/api

Requests and responses are JSON. All timestamps are ISO 8601 in UTC. All resource identifiers exposed through the external API are UUIDs.

Authentication

Every request to the Muzeek API is authenticated with an API key. Pass it as Authorization: Bearer or as the X-API-Key HTTP header.

curl https://muzeek.ai/api/events \
  -H "Authorization: Bearer mzk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Equivalent header:

curl https://muzeek.ai/api/events \
  -H "X-API-Key: mzk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

MCP

External models (Claude, ChatGPT, Gemini, Copilot, Poly) call a curated set of Muzeek tools over Streamable HTTP. Tool results are JSON. The public URL is:

https://muzeek.ai/mcp

Claude, ChatGPT, Gemini, and Microsoft Copilot sign in over OAuth. Add the URL in the assistant — you will be asked to pick an Account. Poly and scripts use an API key with Authorization: Bearer or X-API-Key.

API key example for Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "muzeek": {
      "url": "https://muzeek.ai/mcp",
      "headers": {
        "Authorization": "Bearer mzk_live_your_api_key_here"
      }
    }
  }
}

MCP requests share the standard API-key hourly window (1,000 requests) and the same X-RateLimit-* headers as the REST API.

MCP tools

v1 is an allowlist, not the full in-app assistant surface. Resource identifiers are UUIDs.

MCP does not delete events or bookings, and it does not void invoices.

Booking workflow

Creating and sending a booking is three separate tool calls after you have an event UUID.

Permission scopes

Each API key is granted one or more scopes. Events endpoints require one of:

A key with the wildcard * scope has full access to every endpoint. We recommend issuing narrowly-scoped keys per integration.

MCP is a curated account tool list, not a second REST scope catalogue. On an API key, only createEvent requires write:events. Other MCP tools stay available so a booking loop can run without booking or invoice write scopes. OAuth connections run with *.

Pagination

List endpoints accept page and limit query parameters. The default page size is 10; the maximum is 100. Responses return both the requested slice and pagination metadata:

{
  "data": [ /* array of events */ ],
  "pagination": {
    "page": 1,
    "limit": 10,
    "total": 247,
    "totalPages": 25
  }
}

Including related data

By default, event responses contain only the event record itself. Use the include query parameter to embed related resources in the response.

Combine values with commas, e.g. ?include=venue.full,tour,account.

Errors

All errors use a consistent JSON envelope and the HTTP status code reflects the error class.

{
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid or expired API key"
  }
}

Rate limits

Every API key is rate limited on a rolling hourly window:

• 1,000 requests per hour across read endpoints (GET)
• 200 requests per hour across write endpoints (POST, PUT, DELETE)

These are our current limits. If you have a use case that needs more headroom, get in touch.

Every response includes the following headers so your client can pace itself: