Schedule maintenance
statusio_schedule_maintenanceDestructive
WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | Planned end, 'YYYY-MM-DD HH:mm' (24-hour); after the start. | |
| name | Yes | Short maintenance title. | |
| start | Yes | Planned start, 'YYYY-MM-DD HH:mm' (24-hour). Status.io's reference does not state the time zone of this input: check the scheduled time in your dashboard. | |
| details | Yes | Message describing the maintenance. | |
| automation | No | Start and end the maintenance automatically at the planned times (default false). | |
| notify_now | No | Tell subscribers right away (default false). | |
| notify_1_hr | No | Remind subscribers 1 hour before the start (default false). | |
| notify_24_hr | No | Remind subscribers 24 hours before the start (default false). | |
| notify_72_hr | No | Remind subscribers 72 hours before the start (default false). | |
| statuspage_id | No | Status page id. Defaults to the status page chosen when you connected. | |
| message_subject | No | Subject line for the email notifications. | |
| automation_stop_text | No | Message posted when the maintenance ends (with automation). | |
| automation_start_text | No | Message posted when the maintenance starts (with automation). | |
| infrastructure_affected | No | Affected pairs, each '<component_id>-<container_id>' (ids from statusio_list_components). | |
| all_infrastructure_affected | No | true = every component and container is affected. Otherwise give infrastructure_affected. |