Delete route connection

DELETE

/routes/{route-id}/routecon/{index}

Last modified:2026-09-26 18:00:37

OperationId:DeleteRouteCon

Removes one connection from a route. Requires Super User scope. Other scopes, Reseller included, get 403. The API publishes the change on the service bus (SBUS) NmsRoute channel, and core applies it when the event arrives, so 202 means published, not applied.

The API does not check that the connection exists, so an unknown one also returns 202. The route's other connections keep their indexes.

Send synchronous=yes, in the body or the query string, to wait up to 2 seconds for the connection to be gone. You then get 200. If it is not gone in time, you get the usual 202.

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/json

Examples

Responses

🟢200OK

application/json

Returned for synchronous=yes once the connection is gone.

Bodyapplication/json

🟢202Accepted

🟠400Bad Request

🟠401Authentication Required

🟠404Record not found

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/routes/c2lwOjE4MDAqQCo/routecon/2' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "synchronous": "yes"
}'

Response Example

200 - Wait for the delete

The connection is gone.

{
    "code": 200,
    "message": "Success"
}

Modified at 2026-09-26 18:00:37

Delete route

List route connections