Delete user MoH file

DELETE

/domains/{domain}/users/{user}/moh/{index}

Last modified:2026-10-09 00:31:58

OperationId:DeleteMohUser

Deletes the MoH file at index and its metadata. The other files keep their indexes, so the order has a gap until you reorder or add a file there.

Any user can delete their own MoH. Site Manager can delete the MoH of users in their own site, Office Manager and Call Center Supervisor any user in their domain, a Reseller any user in its territory, and Super User any user. Read-only scopes get 403.

The file is removed on the server that handles the request, before the response, and the removal is copied to the other servers over the SBUS file journal. The call answers 202 by default. An index with no file returns 404. Close the gap with PUT on /domains/{domain}/users/{user}/moh/reorder.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Responses

🟢202Accepted

application/json

The file is deleted on this server and the removal is being copied to the others.

Bodyapplication/json

🟠404

🟠400

🟠401

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//moh/2' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Deleted

The file is deleted.

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

Modified at 2026-10-09 00:31:58

Reorder user MoH files

Read user MoH file