---
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
  - `muting_rule` Configv1MutingRule
    - `slug` string — Unique identifier of the MutingRule. If a `slug` isn't provided, one will be generated based of the `name` field. You can't modify this field after the MutingRule is created.
    - `name` string — Required. Name of the MutingRule. You can modify this value after the MutingRule is created.
    - `created_at` string, date-time — Timestamp of when the MutingRule was created. Cannot be set by clients.
    - `updated_at` string, date-time — Timestamp of when the MutingRule was last updated. Cannot be set by clients.
    - `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.
      - `type` 'EXACT' | 'REGEX' | 'NOT_EXACT' | 'NOT_REGEXP'
      - `name` string — Required. Always matches against an exact label name.
      - `value` string — Required. Matches against a label value based on the configured type.
    - `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.
    - `ends_at` string, date-time — Required. Timestamp of when the muting rule stops being active.
    - `comment` string — Descriptive comment that explains why the muting rule was created.
  - `dry_run` boolean — If true, the MutingRule isn't created, and no response MutingRule will be returned. The response will return an error if the given MutingRule is invalid.

## Response `200`

A successful response containing the created MutingRule.

- Configv1CreateMutingRuleResponse
  - `muting_rule` Configv1MutingRule
    - `slug` string — Unique identifier of the MutingRule. If a `slug` isn't provided, one will be generated based of the `name` field. You can't modify this field after the MutingRule is created.
    - `name` string — Required. Name of the MutingRule. You can modify this value after the MutingRule is created.
    - `created_at` string, date-time — Timestamp of when the MutingRule was created. Cannot be set by clients.
    - `updated_at` string, date-time — Timestamp of when the MutingRule was last updated. Cannot be set by clients.
    - `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.
      - `type` 'EXACT' | 'REGEX' | 'NOT_EXACT' | 'NOT_REGEXP'
      - `name` string — Required. Always matches against an exact label name.
      - `value` string — Required. Matches against a label value based on the configured type.
    - `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.
    - `ends_at` string, date-time — Required. Timestamp of when the muting rule stops being active.
    - `comment` string — Descriptive comment that explains why the muting rule was created.

## 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/config-v1-api.md) · [All operations](https://skmtc.net/chronosphere/apis/config-v1-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chronosphere/config-v1-api/versions/530951bd2ccf/schema)