Meeting ratings

Create and update meeting ratings with complete curl request examples.

Collection path: events/{event_id}/meeting-ratings

Input	Type	POST	PATCH	Notes
`simple_rateable_id`	Scalar ID	Required for a successful create	Rejected if supplied	Meeting must belong to the event and be accepted.
`registrant_id`	Scalar ID	Required for a successful create	Rejected if supplied	Registrant must belong to the event, have a Brella user, and participate in the meeting.
`score`	Integer	Required by the model	Optional	`0` represents skipped; accepted range is `0` to `50`.
`comment`	Scalar string or `null`	Optional	Optional	Rating comment.

POST a meeting rating

POST is an upsert for the meeting and registrant pair. Repeating the request updates the existing rating rather than creating a duplicate.

curl --request POST \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/meeting-ratings" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "simple_rateable_id": 6001,
    "registrant_id": 1201,
    "score": 5,
    "comment": "A useful conversation"
  }'

The response type is meeting-rating. Useful write-response fields include simple_rateable_id (returned as meeting-id), registrant_id, score, comment, and skipped.

PATCH a meeting rating

curl --request PATCH \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/meeting-ratings/8801" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "score": 4,
    "comment": "Useful follow-up"
  }'

Do not send simple_rateable_id or registrant_id on PATCH. Unlike an unselected parameter, a selected and supplied identity field is explicitly rejected by this mutation.