---
title: "Get all downtimes"
method: GET
path: "/api/v1/downtime"
tags: ["Downtimes"]
deprecated: true
---

# Get all downtimes

`GET /api/v1/downtime`

> **Deprecated.**

Get all scheduled downtimes. **Note:** This endpoint has been deprecated. Please use v2 endpoints.

## Query parameters

- `current_only` boolean
- `with_creator` boolean

## Response `200`

OK

- Downtime[]
  - `active` boolean — If a scheduled downtime currently exists.
  - `active_child` DowntimeChild, nullable — The downtime object definition of the active child for the original parent recurring downtime. This field will only exist on recurring downtimes.
    - `active` boolean — If a scheduled downtime currently exists.
    - `canceled` integer, nullable — If a scheduled downtime is canceled.
    - `creator_id` integer — User ID of the downtime creator.
    - `disabled` boolean — If a downtime has been disabled.
    - `downtime_type` integer — `0` for a downtime applied on `*` or all, `1` when the downtime is only scoped to hosts, or `2` when the downtime is scoped to anything but hosts.
    - `end` integer, nullable — POSIX timestamp to end the downtime. If not provided, the downtime is in effect indefinitely until you cancel it.
    - `id` integer — The downtime ID.
    - `message` string, nullable — A message to include with notifications for this downtime. Email notifications can be sent to specific users by using the same `@username` notation as events.
    - `monitor_id` integer, nullable — A single monitor to which the downtime applies. If not provided, the downtime applies to all monitors.
    - `monitor_tags` string[] — A comma-separated list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match ALL provided monitor tags. For example, `service:postgres` **AND** `team:frontend`.
    - `mute_first_recovery_notification` boolean — If the first recovery notification during a downtime should be muted.
    - `notify_end_states` NotifyEndState[] — States for which `notify_end_types` sends out notifications for.
    - `notify_end_types` NotifyEndType[] — If set, notifies if a monitor is in an alert-worthy state (`ALERT`, `WARNING`, or `NO DATA`) when this downtime expires or is canceled. Applied to monitors that change states during the downtime (such as from `OK` to `ALERT`, `WARNING`, or `NO DATA`), and to monitors that already have an alert-worthy state when downtime begins.
    - `parent_id` integer, nullable — ID of the parent Downtime.
    - `recurrence` DowntimeRecurrence, nullable — An object defining the recurrence of the downtime.
      - `period` integer — How often to repeat as an integer. For example, to repeat every 3 days, select a type of `days` and a period of `3`.
      - `rrule` string — The `RRULE` standard for defining recurring events (**requires to set "type" to rrule**) For example, to have a recurring event on the first day of each month, set the type to `rrule` and set the `FREQ` to `MONTHLY` and `BYMONTHDAY` to `1`. Most common `rrule` options from the [iCalendar Spec](https://tools.ietf.org/html/rfc5545) are supported. **Note**: Attributes specifying the duration in `RRULE` are not supported (for example, `DTSTART`, `DTEND`, `DURATION`). More examples available in this [downtime guide](https://docs.datadoghq.com/monitors/guide/suppress-alert-with-downtimes/?tab=api)
      - `type` string — The type of recurrence. Choose from `days`, `weeks`, `months`, `years`, `rrule`.
      - `until_date` integer, nullable — The date at which the recurrence should end as a POSIX timestamp. `until_occurences` and `until_date` are mutually exclusive.
      - `until_occurrences` integer, nullable — How many times the downtime is rescheduled. `until_occurences` and `until_date` are mutually exclusive.
      - `week_days` string[], nullable — A list of week days to repeat on. Choose from `Mon`, `Tue`, `Wed`, `Thu`, `Fri`, `Sat` or `Sun`. Only applicable when type is weeks. First letter must be capitalized.
    - `scope` string[] — The scope(s) to which the downtime applies and must be in `key:value` format. For example, `host:app2`. Provide multiple scopes as a comma-separated list like `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (`env:dev` **AND** `env:prod`).
    - `start` integer — POSIX timestamp to start the downtime. If not provided, the downtime starts the moment it is created.
    - `timezone` string — The timezone in which to display the downtime's start and end times in Datadog applications.
    - `updater_id` integer, nullable — ID of the last user that updated the downtime.
  - `canceled` integer, nullable — If a scheduled downtime is canceled.
  - `creator_id` integer — User ID of the downtime creator.
  - `disabled` boolean — If a downtime has been disabled.
  - `downtime_type` integer — `0` for a downtime applied on `*` or all, `1` when the downtime is only scoped to hosts, or `2` when the downtime is scoped to anything but hosts.
  - `end` integer, nullable — POSIX timestamp to end the downtime. If not provided, the downtime is in effect indefinitely until you cancel it.
  - `id` integer — The downtime ID.
  - `message` string, nullable — A message to include with notifications for this downtime. Email notifications can be sent to specific users by using the same `@username` notation as events.
  - `monitor_id` integer, nullable — A single monitor to which the downtime applies. If not provided, the downtime applies to all monitors.
  - `monitor_tags` string[] — A comma-separated list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match ALL provided monitor tags. For example, `service:postgres` **AND** `team:frontend`.
  - `mute_first_recovery_notification` boolean — If the first recovery notification during a downtime should be muted.
  - `notify_end_states` NotifyEndState[] — States for which `notify_end_types` sends out notifications for.
  - `notify_end_types` NotifyEndType[] — If set, notifies if a monitor is in an alert-worthy state (`ALERT`, `WARNING`, or `NO DATA`) when this downtime expires or is canceled. Applied to monitors that change states during the downtime (such as from `OK` to `ALERT`, `WARNING`, or `NO DATA`), and to monitors that already have an alert-worthy state when downtime begins.
  - `parent_id` integer, nullable — ID of the parent Downtime.
  - `recurrence` DowntimeRecurrence, nullable — An object defining the recurrence of the downtime.
    - `period` integer — How often to repeat as an integer. For example, to repeat every 3 days, select a type of `days` and a period of `3`.
    - `rrule` string — The `RRULE` standard for defining recurring events (**requires to set "type" to rrule**) For example, to have a recurring event on the first day of each month, set the type to `rrule` and set the `FREQ` to `MONTHLY` and `BYMONTHDAY` to `1`. Most common `rrule` options from the [iCalendar Spec](https://tools.ietf.org/html/rfc5545) are supported. **Note**: Attributes specifying the duration in `RRULE` are not supported (for example, `DTSTART`, `DTEND`, `DURATION`). More examples available in this [downtime guide](https://docs.datadoghq.com/monitors/guide/suppress-alert-with-downtimes/?tab=api)
    - `type` string — The type of recurrence. Choose from `days`, `weeks`, `months`, `years`, `rrule`.
    - `until_date` integer, nullable — The date at which the recurrence should end as a POSIX timestamp. `until_occurences` and `until_date` are mutually exclusive.
    - `until_occurrences` integer, nullable — How many times the downtime is rescheduled. `until_occurences` and `until_date` are mutually exclusive.
    - `week_days` string[], nullable — A list of week days to repeat on. Choose from `Mon`, `Tue`, `Wed`, `Thu`, `Fri`, `Sat` or `Sun`. Only applicable when type is weeks. First letter must be capitalized.
  - `scope` string[] — The scope(s) to which the downtime applies and must be in `key:value` format. For example, `host:app2`. Provide multiple scopes as a comma-separated list like `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (`env:dev` **AND** `env:prod`).
  - `start` integer — POSIX timestamp to start the downtime. If not provided, the downtime starts the moment it is created.
  - `timezone` string — The timezone in which to display the downtime's start and end times in Datadog applications.
  - `updater_id` integer, nullable — ID of the last user that updated the downtime.

## Other responses

- `403` — Forbidden
- `429` — Too many requests

---

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