Update responder

Developing

PUT

/responders/{responder-id}

Last modified:2026-10-30 19:17:12

OperationId:UpdateResponder

Changes a responder. Changing a stock responder stores a custom copy with your changes, which reads back as overridden; the stock entry itself is never changed. The change takes effect on each server after its next call engine (NMS) restart. 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

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted. Every server receives the change shortly after, and applies it after its next call engine (NMS) restart.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Not Found

🔴500Internal Server Error

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/responders/c2lwOnN0YXJ0QHRvLXZtYWls' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "responder-name": "To V-Mail (custom)",
    "responder-filename": "custom-vm-intro.wav"
}'

Response Example

202 - Success Example

{
    "responder-id": "c2lwOnN0YXJ0QHRvLXZtYWls",
    "responder-match": "sip:start@to-vmail",
    "responder-source": "overridden",
    "responder-applies": "on-restart"
}

Modified at 2026-10-30 19:17:12

Read responder

Delete custom responder