Customize stock responder

Developing

POST

/responders/{responder-id}/customize

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

OperationId:CustomizeResponder

Copies a stock responder into your custom entries, so you can change it without losing the change on the next upgrade. Fields in the body are applied to the copy, which then reads back as overridden. 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

Query Params

Body Params application/json

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

🟠405Method Not Allowed

🟠409Conflict

🔴500Internal Server Error

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/responders/c2lwOnN0YXJ0QHRvLXZtYWls/customize?overwrite=no' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "responder-name": "Hang Up (custom)"
}'

Response Example

202 - Success Example

{
    "responder-id": "SGFuZ3Vw",
    "responder-match": "Hangup",
    "responder-source": "overridden",
    "responder-applies": "on-restart"
}

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

Delete custom responder

List dial rule applications