How to enable an account as a moderator

Use this guide when you need to grant the moderator role to a participant account for a given event. This is a prerequisite before the account can be assigned as a moderator on any session via POST /api/v2/sessions/set.

Request — enable 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 "email=alex.johnson@example.com" \
  -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 "email=alex.johnson@example.com" \
  -F "moderator=false"

Response

JSON

{
  "code": 200,
  "errors": null,
  "data": {
    "id": 18861,
    "email": "alex.johnson@example.com",
    "status": "updated",
    "external_id": null,
    "moderator": true
  }
}

The moderator: true field in the response confirms the role was attached.

What happens next

Once moderator=true is set, the account becomes available in the moderator pool for this event. You can then assign them to specific sessions via POST /api/v2/sessions/set using the moderators[] parameter (pass the account's ID or email).

Note: Setting moderator=true registers the account as a moderator for the event — it does not automatically assign them to any session. Session assignment is a separate step via POST /api/v2/sessions/set.

Combining speaker and moderator roles

An account can hold both roles simultaneously:

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 "email=alex.johnson@example.com" \
  -F "speaker=true" \
  -F "moderator=true"

Notes

Both roles are event-scoped — the same account can have different roles on different events
Can be set or removed at any time alongside other account updates