Update conference responder

Developing

PUT

/conference-servers/responders/{responder}

Last modified:2026-10-30 22:38:55

OperationId:UpdateConferenceServerResponder

Changes a responder on every Conference server, or on the one config-server names. An update cannot change responder-match-pattern: delete the responder and create the new one. Requires Super User scope.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Query Params

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted. The change is applied shortly after on every Conference server, or only on the one config-server names.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

🔴502Bad Gateway

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/conference-servers/responders/sip:*@check-pin-1?config-server=core1-phx.example.net' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "responder-audio-file": "phrase-get-password-retry.wav"
}'

Response Example

202 - Success Example

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

Modified at 2026-10-30 22:38:55

Read conference responder

Delete conference responder