---
title: "Create group rule"
method: POST
path: "/groups/{groupId}/rules"
tags: ["Group rules"]
---

# Create group rule

`POST /groups/{groupId}/rules`

Adds a rule to the list of rules that get applied to an artifact in the group when adding new
versions.  All configured rules must pass to successfully add a new artifact version.

This operation can fail for the following reasons:

* No group with this `groupId` exists (HTTP error `404`)
* Rule (named in the request body) is unknown (HTTP error `400`)
* Rule is already configured (HTTP error `409`)
* A server error occurred (HTTP error `500`)

## Request body

- CreateRule
  - `config` string, required
  - `ruleType` 'VALIDITY' | 'COMPATIBILITY' | 'INTEGRITY'

## Response `204`

The rule was added.

## Other responses

- `400` — Common response for all operations that can return a `400` error.
- `401` — Common response for all operations that can return a `401` error indicating authentication is required.
- `403` — Common response for all operations that can return a `403` error indicating the user is authenticated but not authorized.
- `404` — Common response for all operations that can return a `404` error.
- `409` — Common response used when an input conflicts with existing data.
- `500` — Common response for all operations that can fail with an unexpected server error.

---

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