Changes fields of one CDR export schedule in a domain. Send only the fields to change. Requires Office Manager, Reseller, or Super User scope. Basic User, Call Center Agent, Site Manager, and other scopes limited to their own schedules can update only a schedule scoped to their own extension: any other returns 404.The name and domain come from the path and cannot be changed. When you send schedule-next-run-datetime, schedule-last-run-datetime is recalculated as one data-lookup-window earlier. Send it in RFC 3339, or as YYYY-MM-DD HH:MM:SS with time-zone. It is stored in UTC. With export-method set to email, export-notify-email-enabled is always stored as yes.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. Read the schedule back to confirm it. schedule-user-export-scope is read-only and never changes on update. Echoing the masked export-password from a read keeps the stored password. A schedule that is not in this domain returns 404.
Request
Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Path Params
Body Params application/jsonRequired
Examples
Responses
🟠400
application/json
A field is invalid. The message names it. Causes: an unknown time-zone, an unparseable date or start time, an invalid data-lookup-window, export-methodscp copy, or an export-password that looks masked but is not this schedule's mask. A publish failure over the SBUS also returns 400: retry.