How to assign or remove a speaker or moderator role
Use this guide when you need to add or remove a speaker or moderator role from an existing participant.
Prerequisites
-
Your API key
-
The participant's internal
id,external_id, oremail
Request — assign speaker role
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 "speaker=true"
Request — remove speaker role
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 "speaker=false"
Request — assign moderator role
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 "moderator=true"
Request — remove moderator role
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 "moderator=false"
Response
JSON
{
"code": 200,
"errors": null,
"data": {
"id": 12345,
"email": "john.doe@example.com",
"status": "updated",
"external_id": null,
"info": ["Account match: id"],
"speaker": true,
"errors": []
},
"response_id": "1700000000.12345"
}
The speaker or moderator field appears in the response only when it was explicitly included in the request.
Notes
-
Speaker and moderator are event-level roles — they are scoped to the specific event identified by
event_id -
Both roles can be assigned or removed in the same request by including both parameters
-
Roles can also be assigned during initial participant creation — see the "How to create a participant with a speaker or moderator role" guide