Documentation Index
Fetch the complete documentation index at: https://apidocs.sessionboard.com/llms.txt
Use this file to discover all available pages before exploring further.
This reference documents every endpoint available in the Sessionboard Public API. Endpoint pages are generated from our OpenAPI specification and include request parameters, response schemas, and example payloads.
Base URLs
| Region | Base URL |
|---|
| US | https://public-api.sessionboard.com |
| EU | https://public-api-eu.sessionboard.com |
Authentication
All requests require an x-access-token header containing a valid API token. See Authentication for details on generating and managing tokens.
curl -H "x-access-token: YOUR_TOKEN" https://public-api.sessionboard.com/v1/events
Common Patterns
Search endpoints accept page and pageSize parameters and return a pagination object in the response. The default page size is 25 and the maximum is 100.
Filtering
POST-based search endpoints accept filter criteria in the request body. Refer to each endpoint’s documentation for available filter fields.
Create vs Search Endpoints
Some resources have two POST endpoints at similar paths:
| Path Pattern | Purpose |
|---|
POST /v1/event/{eventId}/sessions | Search sessions with filters, sorting, and pagination |
POST /v1/event/{eventId}/sessions/create | Create a new session |
/create suffix distinguishes write operations from search. This pattern applies to sessions, contacts, exhibitors, sponsors, custom fields, and all metadata entities.
Sorting
POST-based search endpoints accept a sort object in the request body to control result ordering. Sort by createdAt or updatedAt with asc or desc direction.
Expanding Records
Some endpoints support an expand query parameter to include additional data in the response. Currently, the supported expansion is translated_fields, which returns translated versions of text fields when your event has translations enabled.
Organization-Scoped vs Convenience Routes
Dashboards, widgets, and saved reports support three route patterns:
| Pattern | Example | Notes |
|---|
| Event-scoped | /v1/event/{eventId}/dashboards | Scoped to a single event |
| Org-scoped | /v1/organization/{orgId}/dashboards | Cross-event, explicit org ID |
| Convenience | /v1/dashboards | Cross-event, org resolved from token |
/v1/organization/{orgId}/...) are equivalent but require the org ID in the URL.
Error Codes
| Status Code | Description |
|---|
200 | Success. The response body contains the requested data. |
400 | Bad Request. The request body or parameters are invalid. Check the error message for details. |
401 | Unauthorized. The x-access-token header is missing or the token is invalid. |
403 | Forbidden. The token does not have the required scope for this endpoint. |
404 | Not Found. The requested resource does not exist. |
409 | Conflict. The resource was modified since you last fetched it. Re-fetch the resource to get the current updated_at value and retry your update. |
429 | Too Many Requests. You are being rate limited. Retry after a short delay with exponential backoff. |
500 | Internal Server Error. An unexpected error occurred. Contact support if the issue persists. |
