---
title: "POST /reporting/schedules"
method: POST
path: "/reporting/schedules"
tags: ["Reports"]
---

# POST /reporting/schedules

`POST /reporting/schedules`

Create a new schedule object for reports.

## Request body

- ReportingReportScheduleCreate — Create Report Schedule. Represents an object required to be passed to create new schedule. `name` -- name of the schedule. It will be put as a report name constructed as the following string: "`schedule.name` from `Y-m-d H:i:s` (UTC)". `description` -- description of the schedule. It will be put as the description of the generated report. `trigger` -- trigger configuration of the schedule. `parameters` -- list of parameters required for the report.
  - `name` string, required
  - `description` string, nullable
  - `trigger` ReportingReportScheduleTrigger, required — Report Schedule Trigger details. A report schedule trigger provides information about report execution trigger. `frequency` -- frequency of the schedule, one of: `daily` | `weekly` | `monthly`. `time` -- time of the day in UTC report has to be executed (best-effort approach). `day_of_week` -- day of the week trigger is executed. 1-7: Can be null. In case if the frequency is `daily`, this is ignored. 1 - Monday, 7 - Sunday. `day_of_month` -- day of the month trigger is executed. 1-31: can be null. In case if the frequency is `daily`, this is ignored. If current month has no day number set (i.e. February has no day #31) -- report is not executed this month.
    - `frequency` 'daily' | 'weekly' | 'monthly', required
    - `time` string, required
    - `day_of_week` integer, nullable
    - `day_of_month` integer, nullable
  - `parameters` object[], nullable
  - `renderer` string
  - `template` ReportingReportScheduleTemplateCreate, required — ReportSchedule template id. `id` -- id of the report template
    - `id` string, required

## Response `201`

- ReportingReportScheduleCreate — Create Report Schedule. Represents an object required to be passed to create new schedule. `name` -- name of the schedule. It will be put as a report name constructed as the following string: "`schedule.name` from `Y-m-d H:i:s` (UTC)". `description` -- description of the schedule. It will be put as the description of the generated report. `trigger` -- trigger configuration of the schedule. `parameters` -- list of parameters required for the report.
  - `name` string, required
  - `description` string, nullable
  - `trigger` ReportingReportScheduleTrigger, required — Report Schedule Trigger details. A report schedule trigger provides information about report execution trigger. `frequency` -- frequency of the schedule, one of: `daily` | `weekly` | `monthly`. `time` -- time of the day in UTC report has to be executed (best-effort approach). `day_of_week` -- day of the week trigger is executed. 1-7: Can be null. In case if the frequency is `daily`, this is ignored. 1 - Monday, 7 - Sunday. `day_of_month` -- day of the month trigger is executed. 1-31: can be null. In case if the frequency is `daily`, this is ignored. If current month has no day number set (i.e. February has no day #31) -- report is not executed this month.
    - `frequency` 'daily' | 'weekly' | 'monthly', required
    - `time` string, required
    - `day_of_week` integer, nullable
    - `day_of_month` integer, nullable
  - `parameters` object[], nullable
  - `renderer` string
  - `template` ReportingReportScheduleTemplateCreate, required — ReportSchedule template id. `id` -- id of the report template
    - `id` string, required

## Other responses

- `400`

---

[API](https://skmtc.net/cloudblue/apis/cloudblue-connect-api.md) · [All operations](https://skmtc.net/cloudblue/apis/cloudblue-connect-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cloudblue/cloudblue-connect-api/revisions/0421d2a97c52/schema)