Delete A Specific Route connection

DELETE

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

Last modified:2026-07-28 18:36:59

OperationId:DeleteRouteCon

Delete A Specific Route connection.

Set synchronous to yes in the request body to block until the write has been applied and is readable, and receive a 200 with the resource instead of a 202. Route writes are published to the SBUS NmsRoute channel and applied asynchronously, so without this flag an immediate read-back can miss the record. The API polls for up to 2 seconds; if the write has not landed by then the usual 202 Accepted is returned and the write still completes normally. Note that synchronous must be sent in the JSON body — including on DELETE — as query parameters are not read for write methods.

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 when synchronous=yes and the write has been confirmed readable.

Bodyapplication/json

🟢202Accepted

🟠400Bad Request

🟠401Authentication Required

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

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

Response Example

200 - Example 1

{
    "code": 0,
    "message": "string"
}

Modified at 2026-07-28 18:36:59

Delete A Specific Route

List Route Profiles for a Domain