---
title: "Create a monitor notification rule"
method: POST
path: "/api/v2/monitor/notification_rule"
tags: ["Monitors"]
---

# Create a monitor notification rule

`POST /api/v2/monitor/notification_rule`

Creates a monitor notification rule.

## Request body

- MonitorNotificationRuleCreateRequest — Request for creating a monitor notification rule.
  - `data` MonitorNotificationRuleCreateRequestData, required — Object to create a monitor notification rule.
    - `attributes` MonitorNotificationRuleAttributes, required — Attributes of the monitor notification rule.
      - `conditional_recipients` MonitorNotificationRuleConditionalRecipients — Use conditional recipients to define different recipients for different situations. Cannot be used with `recipients`.
        - `conditions` MonitorNotificationRuleCondition[], required — Conditions of the notification rule.
          - `recipients` string[], required — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
          - `scope` string, required — Defines the condition under which the recipients are notified. Supported formats: - Monitor status condition using `transition_type:<status>`, for example `transition_type:is_alert`. - A single tag key:value pair, for example `env:prod`.
        - `fallback_recipients` string[] — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
      - `filter` union — Specifies the matching criteria for monitor notifications.
        - MonitorNotificationRuleFilterTags — Filters monitor notifications by a list of tag key:value pairs.
          - `tags` string[], required — A list of tag key:value pairs (e.g. `team:product`). All tags must match (AND semantics).
        - MonitorNotificationRuleFilterScope — Filters monitor notifications using a scope expression over key:value pairs with boolean logic (AND, OR, NOT).
          - `scope` string, required — A scope expression composed by key:value pairs (e.g. `service:foo`) with boolean operators (AND, OR, NOT) and parentheses for grouping.
      - `name` string, required — The name of the monitor notification rule.
      - `recipients` string[] — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
    - `type` 'monitor-notification-rule' — Monitor notification rule resource type.

## Response `200`

OK

- MonitorNotificationRuleResponse — A monitor notification rule.
  - `data` MonitorNotificationRuleData — Monitor notification rule data.
    - `attributes` MonitorNotificationRuleResponseAttributes — Attributes of the monitor notification rule.
      - `conditional_recipients` MonitorNotificationRuleConditionalRecipients — Use conditional recipients to define different recipients for different situations. Cannot be used with `recipients`.
        - `conditions` MonitorNotificationRuleCondition[], required — Conditions of the notification rule.
          - `recipients` string[], required — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
          - `scope` string, required — Defines the condition under which the recipients are notified. Supported formats: - Monitor status condition using `transition_type:<status>`, for example `transition_type:is_alert`. - A single tag key:value pair, for example `env:prod`.
        - `fallback_recipients` string[] — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
      - `created` string, date-time — Creation time of the monitor notification rule.
      - `filter` union — Specifies the matching criteria for monitor notifications.
        - MonitorNotificationRuleFilterTags — Filters monitor notifications by a list of tag key:value pairs.
          - `tags` string[], required — A list of tag key:value pairs (e.g. `team:product`). All tags must match (AND semantics).
        - MonitorNotificationRuleFilterScope — Filters monitor notifications using a scope expression over key:value pairs with boolean logic (AND, OR, NOT).
          - `scope` string, required — A scope expression composed by key:value pairs (e.g. `service:foo`) with boolean operators (AND, OR, NOT) and parentheses for grouping.
      - `modified` string, date-time — Time the monitor notification rule was last modified.
      - `name` string — The name of the monitor notification rule.
      - `recipients` string[] — A list of recipients to notify. Uses the same format as the monitor `message` field. Must not start with an '@'. Cannot be used with `conditional_recipients`.
    - `id` string — The ID of the monitor notification rule.
    - `relationships` MonitorNotificationRuleRelationships — All relationships associated with monitor notification rule.
      - `created_by` MonitorNotificationRuleRelationshipsCreatedBy — The user who created the monitor notification rule.
        - `data` MonitorNotificationRuleRelationshipsCreatedByData, nullable — Data for the user who created the monitor notification rule.
          - `id` string — User ID of the monitor notification rule creator.
          - `type` 'users' — Users resource type.
    - `type` 'monitor-notification-rule' — Monitor notification rule resource type.
  - `included` MonitorNotificationRuleResponseIncludedItem[] — Array of objects related to the monitor notification rule that the user requested.
    - `attributes` UserAttributes — Attributes of user object returned by the API.
      - `created_at` string, date-time — The ISO 8601 timestamp of when the user account was created.
      - `disabled` boolean — Whether the user account is deactivated. Disabled users cannot log in.
      - `email` string — The email address of the user, used for login and notifications.
      - `handle` string — The unique handle (username) of the user, typically matching their email prefix.
      - `icon` string — URL of the user's profile icon, typically a Gravatar URL derived from the email address.
      - `last_login_time` string, date-time, nullable — The ISO 8601 timestamp of the user's most recent login, or null if the user has never logged in.
      - `mfa_enabled` boolean — Whether multi-factor authentication (MFA) is enabled for the user's account.
      - `modified_at` string, date-time — The ISO 8601 timestamp of when the user account was last modified.
      - `name` string, nullable — The full display name of the user as shown in the Datadog UI.
      - `service_account` boolean — Whether this is a service account rather than a human user. Service accounts are used for programmatic API access.
      - `status` string — The current status of the user account (for example, `Active`, `Pending`, or `Disabled`).
      - `title` string, nullable — The job title of the user (for example, "Senior Engineer" or "Product Manager").
      - `uuid` string — The globally unique identifier (UUID) of the user.
      - `verified` boolean — Whether the user's email address has been verified.
    - `id` string — ID of the user.
    - `relationships` UserResponseRelationships — Relationships of the user object returned by the API.
      - `org` RelationshipToOrganization — Relationship to an organization.
        - `data` RelationshipToOrganizationData, required — Relationship to organization object.
          - `id` string, required — ID of the organization.
          - `type` 'orgs', required — Organizations resource type.
      - `other_orgs` RelationshipToOrganizations — Relationship to organizations.
        - `data` RelationshipToOrganizationData[], required — Relationships to organization objects.
          - `id` string, required — ID of the organization.
          - `type` 'orgs', required — Organizations resource type.
      - `other_users` RelationshipToUsers — Relationship to users.
        - `data` RelationshipToUserData[], required — Relationships to user objects.
          - `id` string, required — A unique identifier that represents the user.
          - `type` 'users', required — Users resource type.
      - `roles` RelationshipToRoles — Relationship to roles.
        - `data` RelationshipToRoleData[] — An array containing type and the unique identifier of a role.
          - `id` string — The unique identifier of the role.
          - `type` 'roles' — Roles type.
    - `type` 'users' — Users resource type.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `429` — Too many requests

---

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