Update a report schedule
Replaces a report schedule's cadence, recipients, report type, language, timezone and frozen report parameters.
Parameters
| Field | Type | Description |
|---|---|---|
scheduleID required | uuid | path parameter |
Body
The 4 fields most calls use come first; the rest are grouped below.
1 to 200 characters without line breaks.
1 to 50 distinct email addresses.
Timing4 fields
Required for weekly: 1 (Monday) to 7 (Sunday).
Required for monthly: 1 to 28.
Hour of the day, 0 to 23, in timezone. 0 when omitted.
IANA time zone; UTC when omitted.
Delivery3 fields
Defaults to pdf.
en or de (a region such as de-DE or the language name is accepted); null or empty inherits from the client, then the Company.
true when omitted, on update too.
Scope and parameters2 fields
Report on one client; omitted means the Company level. On update, omitting it keeps the schedule's client.
Frozen report parameters: preset, from and to (the window, as in the query of the report endpoints), target (SLA target in percent, above 0 up to 100) and filters (monitor, severity and search narrowing; region, tag and group filters are refused). Without a window a weekly schedule reports the last 7 days and a monthly one the previous month.
Returns
A successful request returns 200 with application/json.
Response fields 1 top-level fields
| Field | Type | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
data | ReportSchedule | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ReportSchedule · 21 fields
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Errors
Only the errors this operation can return. Every error uses the same envelope.
| Status | Code | Meaning |
|---|---|---|
| 400 | bad_request | The request is malformed or fails validation. |
| 402 | billing_action_unavailable | The Company's billing state does not allow this action. When: A metered or limited action while the billing state, such as paused or without credit, blocks it; details holds the action and billing_state. Fix: Top up the credit or change the plan, then retry. |
| 404 | not_found | The requested resource does not exist or is outside the caller's scope. |
| 403 | permission_denied | The credentials do not permit this action. |
| 503 | quota_gate_unavailable | The limit check itself failed, so the action was not carried out. When: The quota service could not decide while the request ran. Fix: Retry in a moment; nothing was changed. |
| 403 / 429 | quota_limit_reached | A usage or inventory limit of the Company was reached. When: Counters and concurrency limits answer 429 with Retry-After, inventory and capacity limits answer 403; details holds purpose, limit and window. Fix: On 429 wait Retry-After seconds; on 403 free something up, request a higher limit where details.raise_request is true, or buy an extension. |
Every call can also return unauthorized (401), rate_limit_exceeded (429) or internal_error (500 / 502). See Responses and errors.