Skip to main content

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.

Webhooks allow your application to receive real-time HTTP callbacks when data changes in Sessionboard. Instead of polling the API for updates, you can subscribe to specific events and receive notifications as they happen.

​
Event Catalog

Subscribe to any combination of the following webhook events.
EventDescription
contact.createdA new contact was created in the organization.
contact.updatedA contact’s details were updated.
contact.deletedA contact was deleted from the organization.
contact.event.associatedA contact was associated with an event.
contact.event.disassociatedA contact was removed from an event.
| Event | Description | | --- | --- | | session.created | A new session was created. | | session.updated | A session’s details were updated. | | session.deleted | A session was deleted. | | session.speaker.attached | A speaker was attached to a session. | | session.speaker.detached | A speaker was detached from a session. |
| Event | Description | | --- | --- | | exhibitor.created | A new exhibitor was created. | | exhibitor.updated | An exhibitor’s details were updated. | | exhibitor.deleted | An exhibitor was deleted. | | exhibitor.event.associated | An exhibitor was associated with an event. | | exhibitor.event.disassociated | An exhibitor was removed from an event. |
EventDescription
sponsor.createdA new sponsor was created.
sponsor.updatedA sponsor’s details were updated.
sponsor.deletedA sponsor was deleted.
sponsor.event.associatedA sponsor was associated with an event.
sponsor.event.disassociatedA sponsor was removed from an event.

​
Payload Structure

Every webhook delivery sends a JSON payload with two top-level keys: data (the full resource that changed) and metadata (information about the event itself).
The data field contains the full resource object for the affected entity (Session, Contact, Sponsor, or Exhibitor). Its shape matches the corresponding response schema in the API Reference.
Example delivery for a session.updated event: 
{
  "data": {
    "id": "fd4e0275-f018-40bc-909a-f8cdfa0df354",
    "sourceOfChange": "user"
  },
  "metadata": {
    "action": "session.updated",
    "actor_id": 7,
    "event_id": 4001,
    "org_id": "757e8d5b-ce66-45f5-ab36-273414f8ab2f",
    "resource_url": "https://public-api.sessionboard.com/v1/event/4001/sessions/fd4e0275-f018-40bc-909a-f8cdfa0df354",
    "version": 1,
    "datetime": "2026-04-28T16:00:00Z"
  }
}
The data object above is abbreviated — production payloads include every field of the resource. Refer to the Session, Contact, Sponsor, and Exhibitor response schemas in the API Reference for the complete shape.

​
Payload Attributes

FieldDescription
data.sourceOfChangeChanges were performed by a user or an agent.
data.idUnique identifier of the affected resource. Always present at the top of data.
metadata.actionThe webhook event type (e.g., session.updated).
metadata.actor_idID of the user who performed the action. null for system-generated events.
metadata.event_idThe Sessionboard event ID associated with the change. null for organization-level events.
metadata.org_idYour organization’s unique identifier.
metadata.resource_urlDirect URL to fetch the full resource from the Public API.
metadata.versionPayload schema version. Currently 1. New non-breaking fields may be added without bumping this.
metadata.datetimeUTC ISO 8601 timestamp of when the event occurred in Sessionboard.
Forward compatibility: Sessionboard may add new fields to data and metadata at any time. Webhook consumers should ignore unknown fields rather than fail on them. Removed or renamed fields will trigger a metadata.version bump.

​
Creating a Webhook

1

Open Webhook Settings

In the Sessionboard admin dashboard, navigate to Settings > Integrations > Webhooks.Webhook settings panel
2

Add an Endpoint

Click Add Endpoint and enter the URL where you want to receive webhook deliveries. This must be a publicly accessible HTTPS endpoint. Select which events you want to subscribe to for this endpoint.Adding a webhook endpoint
3

Save and Activate

Save the webhook configuration. Sessionboard will begin sending events to your endpoint immediately. You can also add custom headers for additional security (e.g., passing a token that your server validates to ensure the request is from Sessionboard).

​
Testing Webhooks

Use the Testing tab on any endpoint to send a sample payload without triggering a real action. You can also use Svix Play to capture and inspect deliveries in a temporary sandbox. Testing a webhook endpoint

​
Monitoring

Sessionboard provides delivery logs for each webhook endpoint in the admin dashboard. You can view recent deliveries, inspect payloads, and check response status codes. Failed deliveries are retried automatically with exponential backoff. Webhook delivery logs