Sessions API

The Sessions API is the programmable side of Sessionboard Sessions. It has its own reference, MCP tools and release notes, apart from the other Sessionboard products.

Base path

Sessions is organization-level, so every operation starts at /v1/organization/{orgId}/sessions-workspace. The same operations are served under /v1/sessions-workspace with the organization taken from the token. They run on the same regional hosts as the rest of the API: public-api.sessionboard.com in the US and public-api-eu.sessionboard.com in the EU.

What you can do

Events

List your Sessions events with their counts, create one, change its name, dates, timezone and location.

Call for speakers

Change what speakers see and when the call closes, close it, and ask to open it.

Submissions and sessions

List what came in, accept or decline each submission, add sessions you invited and import a program.

Agenda, speakers and sponsors

Give sessions a time, room, track and sponsor tags; set the rooms and tracks; read the speakers; ask to publish the agenda to your website.

Opening the call and publishing the agenda are public, so an API call never does them straight away: it answers 202 with status: needs_approval and a link, and a person approves it in Sessions. Accepting or declining sends no email to speakers, and Sessions has no speaker portal.

Your plan’s limits apply to every caller. Past the events a year or the speakers per event your plan includes, a write answers 403 with code: enterprise_only and upgrade naming what needs a bigger plan. When a trial or plan ends, writes answer 403 with code: trial_ended or plan_ended, and everything can still be read.

Sessions needs the read:sessions and write:sessions scopes; see Authentication. AI assistants can do the same work with the Sessions MCP tools. Release notes are in the Sessions changelog.