---
title: "POST /api/v1/config/muting-rules"
method: POST
path: "/api/v1/config/muting-rules"
tags: ["MutingRule"]
---

# POST /api/v1/config/muting-rules

`POST /api/v1/config/muting-rules`

## Request body

- Configv1CreateMutingRuleRequest
  - `dry_run` boolean — If `true`, validates the specified configuration without creating the MutingRule. If the specified configuration is valid, the endpoint returns a partial response without the MutingRule. If the specified configuration is invalid, the endpoint returns an error.
  - `muting_rule` Configv1MutingRule
    - `comment` string — Descriptive comment that explains why the muting rule was created.
    - `created_at` string, date-time — Timestamp of when the MutingRule was created. Cannot be set by clients.
    - `ends_at` string, date-time — Required. Timestamp of when the muting rule stops being active.
    - `label_matchers` Configv1MutingRuleLabelMatcher[] — Required. Specifies which series are silenced by the muting rule. Alerting series must match all muting rule matchers to be silenced. You can't update this value. Updates must specify the original value.
      - `name` string — Required. Always matches against an exact label name.
      - `type` 'EXACT' | 'REGEX' | 'NOT_EXACT' | 'NOT_REGEXP'
      - `value` string — Required. Matches against a label value based on the configured type.
    - `name` string, required — The name of the MutingRule. You can modify this value after the MutingRule is created.
    - `slug` string — The unique identifier of the MutingRule. If a `slug` isn't provided, one is generated based on the `name` field. You can't modify this field after the MutingRule is created.
    - `starts_at` string, date-time — Required. Timestamp of when the muting rule becomes active. You can't update this value. Updates must specify the original value.
    - `updated_at` string, date-time — Timestamp of when the MutingRule was last updated. Cannot be set by clients.

## Response `200`

A successful response containing the created MutingRule.

- Configv1CreateMutingRuleResponse
  - `muting_rule` Configv1MutingRule
    - `comment` string — Descriptive comment that explains why the muting rule was created.
    - `created_at` string, date-time — Timestamp of when the MutingRule was created. Cannot be set by clients.
    - `ends_at` string, date-time — Required. Timestamp of when the muting rule stops being active.
    - `label_matchers` Configv1MutingRuleLabelMatcher[] — Required. Specifies which series are silenced by the muting rule. Alerting series must match all muting rule matchers to be silenced. You can't update this value. Updates must specify the original value.
      - `name` string — Required. Always matches against an exact label name.
      - `type` 'EXACT' | 'REGEX' | 'NOT_EXACT' | 'NOT_REGEXP'
      - `value` string — Required. Matches against a label value based on the configured type.
    - `name` string, required — The name of the MutingRule. You can modify this value after the MutingRule is created.
    - `slug` string — The unique identifier of the MutingRule. If a `slug` isn't provided, one is generated based on the `name` field. You can't modify this field after the MutingRule is created.
    - `starts_at` string, date-time — Required. Timestamp of when the muting rule becomes active. You can't update this value. Updates must specify the original value.
    - `updated_at` string, date-time — Timestamp of when the MutingRule was last updated. Cannot be set by clients.

## Other responses

- `400` — Cannot create the MutingRule because the request is invalid.
- `409` — Cannot create the MutingRule because there is a conflict with an existing MutingRule.
- `500` — An unexpected error response.
- `default` — An undefined error response.

---

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