Create conference

POST

/domains/{domain}/conferences

Last modified:2026-10-09 00:47:37

OperationId:CreateConferenceInDomain

Creates a conference bridge in a domain, with the SIP device and dial rule that route calls to it.

Requires Office Manager scope for your own domain, or Reseller or Super User scope. A Basic User, Simple User, Call Center Agent, or Route Manager can create only an owned conference for their own extension.

There are two kinds of conference:

owned, the default: a personal bridge for an existing user. conference-direct-dial-number is required, and a dial rule sends that number to the bridge. The conference's key becomes conference-owner-user

dedicated: a bridge with its own extension, conference. When the extension has no user yet, a system user with an answering rule and a dial rule is created for it

Setting conference-leader-pin also requires conference-participants-pin, and conference-require-leader-to-start requires a leader PIN. Send PINs and the SIP password themselves: a masked value returns 400.

A 202 means the conference was accepted and is applied shortly after. A conference that already exists, an extension already taken by a user, or a direct-dial number already in use returns 409. A conference-sip-uri or conference-owner-user-id in another domain returns 403.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

The request was accepted. The change is applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

🟠409Conflict

Request Example

Shell

JavaScript

Java

Swift

cURL

Dedicated conferenceOwned conference

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//conferences' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "conference": "3000",
    "conference-type": "dedicated",
    "conference-name": "Sales Bridge",
    "conference-owner-user": "3000",
    "conference-leader-pin": "482915",
    "conference-participants-pin": "073160",
    "limits-max-participants": 15,
    "conference-quorum-minimum-participants": 2,
    "conference-require-leader-to-start": "yes",
    "conference-announce-participants-enabled": "yes",
    "conference-request-name-enabled": "yes"
}'

Response Example

202 - Accepted

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-09 00:47:37

List conference session summaries

Update conference