Sponsor categories

Create and update sponsor categories with complete request examples.

Release timing: This page includes changes planned for 9 October 2026. See the deployment note before using the updated operations or inputs.

Configure an event-level SponsorCategory scope with the needed actions and input mappings. Read access and the optional external_id query field let you reconcile imported categories before creating records.

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request POST \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/sponsor-categories' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "external_id": "CATEGORY-GOLD",
  "name": "Gold",
  "level": "large"
}'

{
  "data": {
    "id": "1201",
    "type": "sponsor-category"
  }
}

Collection path: events/{event_id}/sponsor-categories

POST a sponsor category

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request POST \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/sponsor-categories' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "external_id": "CATEGORY-GOLD",
  "name": "Gold",
  "level": "large",
  "position": 1,
  "allows_meet_at_booth": true
}'

name and level are required. Save data.id from the 201 response. A new category is added to the built-in sponsors page when it exists. Use the returned category ID as category_id when creating sponsors.

PATCH a sponsor category

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request PATCH \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/sponsor-categories/601' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Gold partners"
}'

{
  "data": {
    "id": "1201",
    "type": "sponsor-category"
  }
}

curl --fail-with-body --silent --show-error --globoff --max-time 30 --request PATCH \
  --url "${BRELLA_API_BASE_URL}"'/api/core/organizations/123/events/456/sponsor-categories/601' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Gold partners",
  "position": 2,
  "allows_meet_at_booth": false
}'

The initial request changes only the name. Adding allows_meet_at_booth and changing its value also changes booth permission and use settings for every sponsor in the category. Omit position to retain its current order; null position on PATCH is rejected.

Delete with care

The category DELETE operation removes its sponsors as well. Read and confirm those targets before execution; do not use DELETE merely to rename or reorder a category.

Input reference