Delete CDR schedule

DELETE

/schedule/{schedule_name}

Last modified:2026-09-27 16:26:04

OperationId:DeleteCDRScheduleSystemwide

Deletes one CDR export schedule by name, and the export history records it left. Requires Super User scope for the whole platform. A Reseller can call it too, and is confined to its own territory as if it had called the /resellers/{reseller}/schedule form. Office Manager gets 403: use the /domains/{domain}/schedule form.

The change was published over the service bus (SBUS) and is applied when each server receives it. The body is {"code": 202} with no schedule. A read of the schedule returns 404 once it is applied.

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Path Params

Responses

🟠400

application/json

The delete could not be published over the SBUS. Retry.

Bodyapplication/json

🟠401

🟠404

🟢202Accepted

🟠403Forbidden

Request Example

Shell

JavaScript

Java

Swift

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

Response Example

400 - error

{
    "code": 400,
    "message": "schedule_name required"
}

Modified at 2026-09-27 16:26:04

Update CDR schedule

Read reseller CDR schedule