<!-- WARNING: This documentation is auto-generated from the confluentinc/cli repository and should not be manually edited. -->

<a id="confluent-schema-registry-schema-compatibility-validate"></a>

# confluent schema-registry schema compatibility validate

## Description

Validate that a schema is compatible against a given subject version.

```none
confluent schema-registry schema compatibility validate <schema-path> [flags]
```

## Flags

### Cloud

```none
    --subject string                    REQUIRED: Subject of the schema.
    --type string                       REQUIRED: Specify the schema type as "avro", "json", or "protobuf".
    --version string                    Version of the schema. Can be a specific version or "latest".
    --references string                 The path to the references file.
    --context string                    CLI context name.
    --environment string                Environment ID.
    --schema-registry-endpoint string   The URL of the Schema Registry cluster.
-o, --output string                     Specify the output format as "human", "json", or "yaml". (default "human")
```

### On-Premises

```none
    --subject string                      REQUIRED: Subject of the schema.
    --type string                         Specify the schema type as "avro", "json", or "protobuf".
    --version string                      Version of the schema. Can be a specific version or "latest".
    --references string                   The path to the references file.
    --context string                      CLI context name.
    --certificate-authority-path string   File or directory path to Certificate Authority certificates to authenticate the Schema Registry client.
    --client-cert-path string             File or directory path to client certificate to authenticate the Schema Registry client.
    --client-key-path string              File or directory path to client key to authenticate the Schema Registry client.
    --schema-registry-endpoint string     The URL of the Schema Registry cluster.
-o, --output string                       Specify the output format as "human", "json", or "yaml". (default "human")
```

## Global Flags

```none
-h, --help            Show help for this command.
    --unsafe-trace    Equivalent to -vvvv, but also log HTTP requests and responses which might contain plaintext secrets.
-v, --verbose count   Increase verbosity (-v for warn, -vv for info, -vvv for debug, -vvvv for trace).
```

## Examples

### Cloud

Validate the compatibility of schema “payments” against the latest version of subject “records”.

```none
confluent schema-registry schema compatibility validate payments.avsc --type avro --subject records --version latest
```

### On-Premises

Validate the compatibility of schema “payments” against the latest version of subject “records”.

```none
confluent schema-registry schema compatibility validate payments.avsc --type avro --subject records --version latest --certificate-authority-path <certification-authority-location> --schema-registry-endpoint <schema-registry-endpoint>
```

## See Also

* [confluent schema-registry schema compatibility](index.md#confluent-schema-registry-schema-compatibility) - Manage schema compatibility.