Delete custom responder

Developing

DELETE

/responders/{responder-id}

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

OperationId:DeleteResponder

Deletes a custom responder. An overridden responder goes back to its stock values, and a custom responder with no stock entry is removed. 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

Responses

🟢202Accepted

application/json

Accepted. Every server receives the change shortly after, and applies it after its next call engine (NMS) restart. responder-source is stock when the entry went back to its stock values, or removed.

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 19:17:15

Update responder

Customize stock responder