Delete connection

DELETE

/connections/{connection-id}

Last modified:2026-09-26 20:52:19

OperationId:deleteConnection

Deletes a connection by connection-id, without naming its domain. Requires Office Manager, Route Manager, or Call Center Supervisor scope in the connection's domain, Reseller scope in its territory, or Super User scope. The API publishes the delete on the service bus (SBUS) connection_events channel, and each server removes the row when the event arrives, so 202 means published, not deleted.

An id that names no connection returns 404. One in a domain your scope does not cover returns 403. A route profile's id deletes the profile with its route and route connections.

Read the connection back to confirm it is gone. A connection that another platform service keeps registering, most often an outbound_registration one, can be written back about 30 to 60 seconds after the delete. If it keeps coming back, contact support.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢202

application/json

The delete was published on the SBUS. The row is removed after this response.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/connections/c2lwOipAMTkyLjAuMi4xMA' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Deleted

Published.

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-09-26 20:52:19

Update connection

Count connections