Skip to content
Core API
Esc
↑↓navigate↵open⌘Jpreview
On this page

Session bookmarks

Create and update session bookmarks with complete curl request examples.

Build a request

Example data only. No request is sent.

POST
Choose the destination IDs
Start with these fields

Timeslot must belong to the event.

Registrant must belong to the event.

Use the API address and token from your environment. Set up authentication.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request POST \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/session-bookmarks' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "timeslot_id": 5501,
  "registrant_id": 1201
}'
201 CreatedIllustrative response
{
  "data": {
    "id": "1201",
    "type": "session-bookmark"
  }
}

The token scope determines returned fields. This selector illustrates that configuration; it does not change your token or the request.

Collection path: events/{event_id}/session-bookmarks

POST a session bookmark

View the complete cURL example
curl --fail-with-body --silent --show-error --globoff --max-time 30 --request POST \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/session-bookmarks' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "timeslot_id": 5501,
  "registrant_id": 1201
}'

POST is idempotent for the same timeslot and registrant pair: the existing bookmark is returned instead of creating a duplicate. The response type is session-bookmark; useful write-response fields include timeslot_id, registrant_id, and created_at.

The wrapper declares no PATCH mutation for session bookmarks. Delete and recreate a bookmark only when your scope also grants the available delete action.

Input reference

2 inputs. Expand a field for its request type and update behavior. These are the example request keys; your administrator can configure aliases.

timeslot_idScalar ID
POST
Used
PATCH
Not supported

Timeslot must belong to the event.

registrant_idScalar ID
POST
Used
PATCH
Not supported

Registrant must belong to the event.

Last updated on August 25, 2026