---
title: "Update artifact rule configuration"
method: PUT
path: "/groups/{groupId}/artifacts/{artifactId}/rules/{rule}"
tags: ["Artifact rules"]
---

# Update artifact rule configuration

`PUT /groups/{groupId}/artifacts/{artifactId}/rules/{rule}`

Updates the configuration of a single rule for the artifact.  The configuration data
is specific to each rule type, so the configuration of the `COMPATIBILITY` rule 
is in a different format from the configuration of the `VALIDITY` rule.

This operation can fail for the following reasons:

* No artifact with this `artifactId` exists (HTTP error `404`)
* No rule with this name/type is configured for this artifact (HTTP error `404`)
* Invalid rule type (HTTP error `400`)
* A server error occurred (HTTP error `500`)

## Request body

- Rule
  - `config` string, required
  - `type` 'VALIDITY' | 'COMPATIBILITY' | 'INTEGRITY'

## Response `200`

Rule configuration was updated.

- Rule
  - `config` string, required
  - `type` 'VALIDITY' | 'COMPATIBILITY' | 'INTEGRITY'

## Other responses

- `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.
- `500` — Common response for all operations that can fail with an unexpected server error.

---

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