Events

Create and update events with complete curl request examples.

Build a request

Example data only. No request is sent.

PATCH

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request PATCH \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Customer Summit 2027",
  "start_date": "2027-04-12",
  "end_date": "2027-04-14"
}'

200 OKIllustrative response

Write-response fields

{
  "data": {
    "id": "1201",
    "type": "event"
  }
}

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

Collection path: events at organization level. Core tokens cannot create events.

PATCH an event

View the complete cURL example

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request PATCH \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Customer Summit 2027",
  "start_date": "2027-04-12",
  "end_date": "2027-04-14"
}'

The response type is event. Useful write-response fields are name, start_date, and end_date. A POST to the organization-level events collection is rejected because the Event wrapper declares no create mutation.

Input reference

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

nameScalar string

POST: Not supported
PATCH: Optional

Event name.

start_dateDate string

POST: Not supported
PATCH: Optional

Event start date.

end_dateDate string

POST: Not supported
PATCH: Optional

Event end date.