# Delete a report schedule `DELETE /v1/report-schedules/{reportScheduleId}` Deletes a report schedule at once, so it makes no more snapshots and sends no more emails. It cannot be undone. The snapshots it has already made are kept. Find them in [List reports](https://developers.silktide.com/v1/governance/reports/list-reports.md) by their `reportScheduleId`, and [delete them](https://developers.silktide.com/v1/governance/reports/delete-report.md) one by one if you no longer want them. The response is an empty `201`. Deleting it again returns `404`. The old documentation called the path parameter `{reportId}`. It is the schedule's id, `reportScheduleId`. ## Request ### Path parameters - `reportScheduleId` (integer, required, at least 1): The report schedule. ## Response Status `201`. No body. ## Errors | Status | Type | When | | --- | --- | --- | | 403 | `EditionNotAvailable` | The account does not have Silktide 4. Reports, report schedules and report templates are Silktide 4's, so an account with only Silktide 5 cannot use them. | | 400 | `InvalidRequest` | `reportScheduleId` is not a whole number. `properties.field` is `reportScheduleId`. | | 404 | `ModelNotFound` | No report schedule with that id exists in the account. | | 403 | `AccessDenied` | The API key's user cannot see or admin the report schedule. | | 401 | `NotLoggedIn` | No API key was sent, or it is not a key for this region. | | 429 | `TooManyRequests` | Too many requests to this path in five seconds. Retry after the number of seconds in the `Retry-After` header, which `properties.retryAfter` repeats. | | 503 | - | Silktide is busy. Retry after the number of seconds in the `Retry-After` header. | ## Access - Permission: Can admin this report schedule - Plan feature: none - Edition: Silktide 4 only - Cost: free - Stability: stable, since 1.0.0 ## Example: Delete a report schedule ```bash curl -X DELETE "https://api.eu.silktide.com/v1/report-schedules/2" \ -H "Authorization: silktide token=$SILKTIDE_API_KEY" ```