# Eventdoor developer docs

Eventdoor runs live and on-demand event platforms. These docs cover connecting an AI assistant over MCP and calling the REST API with a scoped API credential.

## For agents

- To act as a person on an Eventdoor platform, connect over MCP at https://mcp.eventdoor.com/eventdoor/api/v1/mcp (OAuth client eventdoor-assistant; Claude and Claude Code only).
- To automate with a token, use the REST API: the OpenAPI spec is at https://docs.eventdoor.com/rest-api/openapi.json and the base URL is https://<your platform's API host>/eventdoor/api/v1.
- Every page has a .md twin, and https://docs.eventdoor.com/llms-full.txt has them all.

# Eventdoor Docs

- [Eventdoor developer docs](/): Connect an AI assistant to Eventdoor, or call the Eventdoor REST API with a scoped API credential.
- AI assistants

  - **Set up**
  - [Connect Claude](/ai-assistants): Add Eventdoor to Claude on the web or desktop as a custom connector.
  - [Connect Claude Code](/ai-assistants/claude-code): Add Eventdoor to Claude Code with one command in a terminal, then sign in from Claude Code as yourself.

  - **Using an assistant**
  - [What an assistant can do](/ai-assistants/permissions): An AI assistant acts as you on Eventdoor: what it can read, what it can change, and what it can never do.
  - [Stay connected and disconnect](/ai-assistants/manage): How an AI assistant stays connected to Eventdoor, how to disconnect it, and how admins manage connected assistants.
  - [Troubleshooting](/ai-assistants/troubleshooting): Fixes for the problems you may hit while connecting an AI assistant to Eventdoor or using it day to day.
- REST API
  - [Get started with the REST API](/rest-api): Issue a scoped API credential and make your first call.
  - [Authentication](/rest-api/authentication): How Eventdoor API credentials authenticate: the bearer token, read and write access, scope, expiry and revoking.

  - **Guides**
  - [Errors and rate limits](/rest-api/errors): What the Eventdoor REST API returns when it refuses a request, and how the per-credential rate limit works.
  - [Pagination](/rest-api/pagination): How Eventdoor REST API list operations page their results with a limit and a cursor.
  - [Bulk operations](/rest-api/bulk): Update or create many broadcasts in one Eventdoor REST API call, and read the result of each row.

  - **Reference**
  - API reference
    - [API reference](/rest-api/reference): Every operation a scoped API credential can call, with its request and response.

    - **Hubs**
    - [List organization hubs](/rest-api/reference/list-org-hubs): Filter by tag categories using query params named after category slugs (e.g. ?age_group=5-8,9-12&sport=swimming). Within a category, values are OR'd; across categories, they are AND'd. Also supports single-value tag / collection / category filters. Use facets=true to include facet counts in the response.
    - [Get hub](/rest-api/reference/get-hub)

    - **Broadcasts**
    - [List broadcasts (org-wide)](/rest-api/reference/list-org-broadcasts): List broadcasts across all hubs belonging to the organization. Supports cross-hub discovery via tag / collection / category filters. Each row's `attachedVod.videoUrl` is null on a paid broadcast unless the caller has bought access to it or is signed in as a member of its organization. An API credential never unlocks paid content, so with one it is null on every paid broadcast.
    - [List broadcasts in hub](/rest-api/reference/list-broadcasts): Filter by tag categories using query params named after category slugs. Within a category, values are OR'd; across categories, they are AND'd. Use facets=true to include facet counts in the response. Each row's `attachedVod.videoUrl` is null on a paid broadcast unless the caller has bought access to it or is signed in as a member of its organization. An API credential never unlocks paid content, so with one it is null on every paid broadcast.
    - [Get broadcast (org-scoped)](/rest-api/reference/get-org-broadcast): Retrieve a broadcast by its slug within the organization scope. Broadcast slugs are unique per organization, so the hub slug is not required to resolve the broadcast.
    - [Get broadcast](/rest-api/reference/get-broadcast)
    - [Create broadcast](/rest-api/reference/create-broadcast)
    - [Update broadcast (org-scoped)](/rest-api/reference/update-org-broadcast): Update a broadcast by its slug within the organization scope. On a VOD-mode broadcast with an attached video, a new title, description or posterUrl also updates that video.
    - [Update broadcast](/rest-api/reference/update-broadcast)
    - [Bulk update broadcasts](/rest-api/reference/bulk-update-broadcasts): Update multiple broadcasts in a single request. Each operation is processed independently (best-effort). Returns 207 with per-item results.
    - [Bulk upsert broadcasts](/rest-api/reference/bulk-upsert-broadcasts): Create or update multiple broadcasts in a single request (e.g. a CSV import/round-trip). An operation with an `id` updates that broadcast in place; without one it creates a new broadcast. Each operation is processed independently (best-effort). Returns 207 with per-item results keyed by an optional client-supplied ref.
    - [List who changed a broadcast, newest first](/rest-api/reference/list-broadcast-changes): Each create, edit, end, reopen, stream key rotation and delete of the broadcast, with who made it and whether it came through the AI assistant or a scoped API credential. An edit lists the fields whose stored value changed; a save that changed nothing is not listed. Organization admins only. Cursor-paginated: pass `paging.next` back as `cursor`.