---
title: "Update subject compatibility level"
method: PUT
path: "/config/{subject}"
tags: ["Config (v1)"]
---

# Update subject compatibility level

`PUT /config/{subject}`

Update compatibility level, compatibility group, normalization,
default metadata, and rule set for the specified subject. On success,
echoes the original request back to the client.

## Path parameters

- `subject` string, required

## Request body

- ConfigUpdateRequest — Config update request
  - `alias` string — If alias is specified, then this subject is an alias for the subject named by the alias. That means that any reference to this subject will be replaced by the alias.
  - `normalize` boolean — If true, then schemas are automatically normalized when registered or when passed during lookups. This means that clients do not have to pass the "normalize" query parameter to have normalization occur.
  - `compatibility` string — Compatibility Level
  - `compatibilityGroup` string — Only schemas that belong to the same compatibility group will be checked for compatibility.
  - `defaultMetadata` object — Default value for the metadata to be used during schema registration.
    - `properties` object — The metadata properties and their new values
  - `overrideMetadata` object — Override value for the metadata to be used during schema registration.
    - `properties` object — The metadata properties and their new values
  - `defaultRuleSet` object — Default value for the ruleSet to be used during schema registration.
    - `properties` object — The metadata properties and their new values
  - `overrideRuleSet` object — Override value for the ruleSet to be used during schema registration.
    - `properties` object — The metadata properties and their new values

## Response `200`

The original request.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `422` — Unprocessable Entity. Error code 42203 indicates invalid compatibility level.
- `429` — Rate Limit Exceeded
- `500` — Internal Server Error. Error code 50001 indicates a failure in the backend data store. Error code 50003 indicates a failure forwarding the request to the primary.

---

[API](https://skmtc.dev/confluent/apis/confluent-cloud-apis.md) · [All operations](https://skmtc.dev/confluent/apis/confluent-cloud-apis/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/confluent/confluent-cloud-apis/revisions/a6a73f98a698/schema)