To follow the feature added in the UI, we added the optional field name in the Session endpoints. You can now use this field as following:

We’re excited to announce that we’re opening a new webhook made to be notified when a someone watches the replay of a session.

We’re excited to announce that we’re opening a new API endpoint meant to retrieve the list of people attributes from your workspace. To use it, simply call this new GET /people_attributes endpoint as follow:

We’re thrilled to announce the launch of our new bulk registration endpoint that lets you register multiple participants at the same time, instead of having to register them individually. This new POST /sessions/:id/people/bulk endpoint is based on an asynchronous, job-based mechanism:

An improvement has been released today regarding "Register someone for a session" endpoint. Email is now the only required field to register someone through the API.

We’re excited to announce that we’re opening a new API endpoint meant to retrieve the questions asked in the dedicated “Questions” tab during a Livestorm event session. To use it, simply call this new GET /sessions/{id}/questions endpoint as follow:

We’re excited to announce that we’re opening a new API endpoint meant to retrieve the recording of a Livestorm event session. To use it, simply call this new GET /sessions/{id}/recordings endpoint as follow:

We’re excited to announce that we’re opening a new API endpoint meant to retrieve the chat messages sent in the dedicated “Chat” tab during a Livestorm event session. To use it, simply call this new GET /sessions/{id}/chat_messages endpoint as follow:

By default, new Livestorm workspaces won’t have access to the REST API. To get access to the API, new customers will simply have to send a message to our support team at [email protected], who might ask a few questions about the planned usage of the API. Don’t worry though, existing customers are not affected by this mandatory check!

We’d like to inform you about the deprecation notice of the event.published webhook subscription, as well as events’ status attribute (that can take the “draft” or “published” value, as of today).