Matchmaking interests

Create and update matchmaking interests with complete curl request examples.

Build a request

Example data only. No request is sent.

POST

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

201 CreatedIllustrative response

Write-response fields

{
  "data": {
    "id": "1201",
    "type": "matchmaking-interest"
  }
}

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}/matchmaking-interests

POST a matchmaking interest

The example creates a child interest under category 700.

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/matchmaking-interests' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Artificial intelligence",
  "parent_id": 700,
  "position": 2,
  "intent_pair_ids": [
    41,
    42
  ]
}'

To create a category, omit parent_id and send no intent pairs. The response type is matchmaking-interest; useful write-response fields include parent_id, name, position, intent_pair_ids, and category.

PATCH a matchmaking interest

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/matchmaking-interests/701' \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
  "name": "Applied artificial intelligence",
  "position": 3,
  "intent_pair_ids": [
    41,
    43
  ]
}'

Setting parent_id to null converts a child into a category only if its resulting intent-pair set is empty.

Input reference

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

parent_idScalar ID or `null`

POST: Optional
PATCH: Optional

No parent means category; a parent must be an interest in the event.

nameScalar string

POST: Optional at wrapper level
PATCH: Optional

Interest name.

positionScalar number or `null`

POST: Optional
PATCH: Optional

Display order.

intent_pair_idsArray of scalar IDs

POST: Optional
PATCH: Optional

Full replacement when supplied. Categories cannot have intent pairs.