How to detach a participant from an exhibitor team

Use this guide when you need to remove a participant's association with an exhibitor team — for example, when a team member leaves a company or was assigned to the wrong exhibitor.

⚠️ Omitting the fields is not enough. To detach a participant from an exhibitor team, you must explicitly pass both exhibitor_id=0 and exhibitor_external_id=0 in the same request. Simply leaving the fields out will leave the current assignment unchanged.

What you'll need before starting

What you need	Where to get it
Participant ID, External ID, or email	`GET /api/v2/account/get` or `GET /api/v2/participants/{eventId}/list`

Request

Bash

curl -X POST "https://your-event-domain.com/api/v2/account/set" \
  -H "Authorization: Bearer your_api_key_here" \
  -F "event_id=7" \
  -F "id=12345" \
  -F "exhibitor_id=0" \
  -F "exhibitor_external_id=0"

Response

JSON

{
  "code": 200,
  "errors": null,
  "data": {
    "id": 12345,
    "email": "john.doe@example.com",
    "status": "updated",
    "external_id": null,
    "info": ["Account match: id"],
    "errors": []
  },
  "response_id": "1700000000.12345"
}

Notes

Both exhibitor_id=0 and exhibitor_external_id=0 must be passed together — one alone is not sufficient to trigger the detachment
The detachment is scoped to the event identified by event_id — the participant's team membership in other events is not affected
Detaching a participant does not delete their account or affect any other profile data
To reassign the participant to a different exhibitor, use a new request with the correct exhibitor_id or exhibitor_external_id — see the "How to assign a participant to an exhibitor team or update their role" guide