Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
    • Service roles for access management
    • Troubleshooting
      • API authentication
      • Schema Registry
  • Access management
  • Quotas and limits
  • Pricing policy
  • Public materials
  • Release notes

In this article:

  • NamespaceService
  • SubjectService
  • SchemaService
  1. Schema Registry
  2. API reference
  3. Schema Registry

Schema Registry API

Written by
Yandex Cloud
Updated at August 25, 2025
  • NamespaceService
  • SubjectService
  • SchemaService

After you authenticate with an IAM token, you can use the following HTTP requests:

NamespaceServiceNamespaceService

Parameter Command Description
/compatibility/rules GET Get default compatibility rules
/compatibility/rules PUT Update default compatibility rules
/config GET Get default compatibility level
/config PUT Update default compatibility level
/v1/namespace GET Get the list of namespaces
/v1/namespace POST Register a namespace
/v1/namespace/{id} GET Get the namespace by its ID
/v1/namespace/{id} DELETE Delete the specified namespace
/v1/namespace/{id} PATCH Delete the specified namespace

SubjectServiceSubjectService

Parameter Command Description
/compatibility/subjects/{subject}/versions POST Test schema compatibility
/compatibility/subjects/{subject}/versions/{version} POST Test schema compatibility
/config/{subject} GET Get compatibility level for the subject
/config/{subject} PUT Update subject compatibility level
/config/{subject} DELETE Delete subject compatibility level
/subjects GET Retrieves a list of registered subjects matching specified parameters
subjects/{subject} POST Lookup schema under subject
subjects/{subject} DELETE Delete the specified subject
/subjects/{subject}/versions GET List versions under subject
/subjects/{subject}/versions POST Register schema under a subject
/subjects/{subject}/versions/{version} GET Get schema by version
/subjects/{subject}/versions/{version} DELETE Delete schema version.
/subjects/{subject}/versions/{version}/referencedby GET List schemas referencing a schema
/subjects/{subject}/versions/{version}/schema GET Get schema by version

SchemaServiceSchemaService

Parameter Command Description
/schemas GET List schemas
/schemas/ids/{id} GET Get schema string by ID
/schemas/ids/{id}/schema GET Get schema string by ID
/schemas/ids/{id}/subjects GET List subjects associated to schema ID
/schemas/ids/{id}/versions GET List subject-versions associated to schema ID
/schemas/types GET List supported schema types

See the following documents for detailed information about working with a Confluent-compatible API:

  • Confluent Schema Registry API reference
  • Examples of using the Confluent Schema Registry API
  • Tutorial on using curl to communicate with Schema Registry

Was the article helpful?

Previous
API authentication
Next
Getting started as a metadata steward
© 2025 Direct Cursus Technology L.L.C.