Delete custom responder

Developing

DELETE

/responders/{responder-id}

Last modified:2026-10-30 17:28:40

OperationId:DeleteResponder

Deletes a custom responder. An overridden responder goes back to its stock values (responder-source stock in the response). A custom responder with no stock entry is removed (removed).

Stock responders cannot be deleted: 409. Removing a custom application that dial rules still use is also 409, and the message gives the number of rules. Pass force=yes to remove it anyway.

The call engine loads responders when it starts, so a change takes effect on each server after its next NMS restart. The call answers 202, the change reaches every server shortly after, and the response says responder-applies: on-restart.

Requires the 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

Responses

🟢202Accepted

application/json

Accepted. Applies on each server after its next NMS restart.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Not Found

🟠409Conflict

🔴500Internal Server Error

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/responders/c2lwOnN0YXJ0QHRvLXZtYWls?force=no' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Success Example

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

Modified at 2026-10-30 17:28:40

Update responder

Customize stock responder