Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Livestorm (BYOK) — connector documentation

  • MCP endpoint: https://byok-livestorm.connectorbay.com/mcp
  • REST API: POST https://byok-livestorm.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-livestorm.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Livestorm Livestorm API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-livestorm.connectorbay.com/health · Tool schemas: https://byok-livestorm.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-livestorm · agent@connectorbay.com

What Livestorm (BYOK) is for

Livestorm (BYOK) lets an AI assistant read your own Livestorm data through the Livestorm API with a key you supply (Livestorm API token). Read-only: 7 tools (get_organization, list_events, get_event, list_event_sessions, list_sessions, get_session, list_session_recordings). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.livestorm.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Livestorm. Livestorm and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Livestorm workspace is this API token for?"
  • "Which upcoming webinars do we have on Livestorm?"
  • "Show me the Livestorm event e1"
  • "When are the sessions of Livestorm event e1 and how many people registered?"
  • "Which Livestorm sessions took place last month and how many attended?"
  • "How many people attended Livestorm session s1?"

What it does

  • get_organization: Get the Livestorm workspace organization: name and slug. Needs a token with the identity or admin scope.
  • list_events: List webinar events (series of sessions) with title, status, scheduling status, language, duration and session count, optionally by title or status.
  • get_event: Get one webinar event by ID: title, status, language, duration, registration link, feature switches and session count.
  • list_event_sessions: List the sessions (dated occurrences) of one event with status, timezone, start and end time, registrant and attendee counts.
  • list_sessions: List all sessions across all events of the workspace with status, start time, registrant and attendee counts, optionally by status and date range.
  • get_session: Get one session by ID: name, status, timezone, start and end time, registrant and attendee counts and duration.
  • list_session_recordings: List the recordings of a session with file type, size and name (the signed download link is not returned).

BYOK key

You bring your own Livestorm Livestorm API token (https://developers.livestorm.co/docs/api-token-authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.livestorm.co over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Livestorm API (api.livestorm.co) with a BYOK key; documentation: https://developers.livestorm.co/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Livestorm. Livestorm and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Livestorm account.

Built for: Worldwide. Languages: English.