Skip to main content
Early Access — Reports, Dashboards, and related query APIs are currently available to select organizations. Reach out to your Sessionboard account manager to get early access.
These endpoints power Reports and Dashboards in Sessionboard — the same surfaces organizers use in the product to explore session and speaker data, run saved reports, and view dashboard widgets. Under the hood, queries use SbQL (Sessionboard Query Language). You can also convert natural language into SbQL, discover the query schema, and connect AI assistants via the MCP Server.
API tokens need the read:insights scope (the scope name is historical; it gates Reports, Dashboards, and SbQL access). See Authentication.

​
Prerequisites

  1. Organization-level: AI features must be enabled for your organization. Contact your Sessionboard account manager.
  2. Who is calling: An assistant signed in with OAuth needs the Connect AI assistants permission. A script using an API token needs read:insights in its scopes (a token with no scopes is the legacy full-access case). There is no separate MCP switch.

​
What this covers

Endpoint paths still use the /v1/insights/... prefix (for example POST /v1/insights/execute, GET /v1/insights/queries). That prefix is the public API namespace — not a separate product called Insights.

​
Learn more

SbQL Reference

Query language syntax, entities, and examples.

MCP Server

Connect Claude and other AI assistants to your event data.

Connect an AI assistant

Step-by-step Help Center guides for Claude, ChatGPT, Copilot, and Gemini.

Generate an API token

Help Center walkthrough of token scopes and PII Obfuscation. Assistants sign in with OAuth.