How to update a participant's connection settings

Use this guide when you need to control whether a participant can receive meeting requests, messages, or engage in chats and meetings on the platform.

Prerequisites

Your API key
The participant's internal id, external_id, or email

Request — disable all incoming connections

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 "allow_receive_requests=0" \
  -F "allow_receive_messages=0" \
  -F "allow_meetings=0" \
  -F "allow_chats=0"

Request — enable all incoming connections

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 "allow_receive_requests=1" \
  -F "allow_receive_messages=1" \
  -F "allow_meetings=1" \
  -F "allow_chats=1"

Request — disable meeting requests only

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 "allow_receive_requests=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"
}

Available connection fields

Parameter	Description	Accepted values	Default on create
`allow_receive_requests`	Controls whether others can send meeting requests	`0` (disabled) or `1` (enabled)	`1`
`allow_receive_messages`	Controls whether others can send messages	`0` (disabled) or `1` (enabled)	`1`
`allow_meetings`	Meetings feature flag	`0` (disabled) or `1` (enabled)	`1`
`allow_chats`	Chat feature flag	`0` (disabled) or `1` (enabled)	`1`

Notes

Include only the fields you want to change — others will remain at their current setting
All four fields use 0 / 1 as integer values, not boolean true/false