Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 4. Managing Apicurio Registry content using the REST API

Client applications can use Registry REST API operations to manage schema and API artifacts in Apicurio Registry, for example, in a CI/CD pipeline deployed in production. The Registry REST API provides create, read, update, and delete operations for artifacts, versions, metadata, and rules stored in the registry. For detailed information, see the Apicurio Registry REST API documentation.

This chapter describes the Apicurio Registry core REST API and shows how to use it to manage schema and API artifacts stored in the registry:

Prerequisites

This section shows a simple curl-based example of using the registry v2 core REST API to add and retrieve an Apache Avro schema artifact in the registry.

Prerequisites

  • Apicurio Registry must be installed and running in your environment.

Procedure

  1. Add an artifact to the registry using the /groups/{group}/artifacts operation. The following example curl command adds a simple artifact for a share price application: 

    $ curl -X POST -H "Content-type: application/json; artifactType=AVRO" \
  -H "X-Registry-ArtifactId: share-price" \
    1 
    
  --data '{"type":"record","name":"price","namespace":"com.example", \
   "fields":[{"name":"symbol","type":"string"},{"name":"price","type":"string"}]}' \
    2 
    
  http://MY-REGISTRY-HOST/apis/registry/v2/groups/my-group/artifacts
    3
    Copy to Clipboard Toggle word wrap
    1
    This example adds an Avro schema artifact with an artifact ID of share-price. If you do not specify a unique artifact ID, Apicurio Registry generates one automatically as a UUID.
    2
    MY-REGISTRY-HOST is the host name on which Apicurio Registry is deployed. For example: my-cluster-service-registry-myproject.example.com.
    3
    This example specifies a group ID of my-group in the API path. If you do not specify a unique group ID, you must specify ../groups/default in the API path.

  2. Verify that the response includes the expected JSON body to confirm that the artifact was added. For example: 

    {"createdBy":"","createdOn":"2021-04-16T09:07:51+0000","modifiedBy":"",
"modifiedOn":"2021-04-16T09:07:51+0000","id":"share-price","version":"1",
    1 
    
"type":"AVRO","globalId":2,"state":"ENABLED","groupId":"my-group","contentId":2}
    2
    Copy to Clipboard Toggle word wrap
    1
    No version was specified when adding the artifact, so the default version 1 is created automatically.
    2
    This was the second artifact added to the registry, so the global ID and content ID have a value of 2.

  3. Retrieve the artifact content from the registry using its artifact ID in the API path. In this example, the specified ID is share-price: 

    $ curl http://MY-REGISTRY-URL/apis/registry/v2/groups/my-group/artifacts/share-price \
{"type":"record","name":"price","namespace":"com.example", \
  "fields":[{"name":"symbol","type":"string"},{"name":"price","type":"string"}]}
    Copy to Clipboard Toggle word wrap

If you do not specify an artifact version when adding schema and API artifacts to Apicurio Registry using the v2 REST API, Apicurio Registry generates one automatically. The default version when creating a new artifact is 1.

Apicurio Registry also supports custom versioning where you can specify a version using the X-Registry-Version HTTP request header as a string. Specifying a custom version value overrides the default version normally assigned when creating or updating an artifact. You can then use this version value when executing REST API operations that require a version.

This section shows a simple curl-based example of using the registry v2 core REST API to add and retrieve a custom Apache Avro schema version in the registry. You can specify custom versions when using the REST API to add or update artifacts or to add artifact versions.

Prerequisites

  • Apicurio Registry must be installed and running in your environment.

Procedure

  1. Add an artifact version in the registry using the /groups/{group}/artifacts operation. The following example curl command adds a simple artifact for a share price application: 

    $ curl -X POST -H "Content-type: application/json; artifactType=AVRO" \
  -H "X-Registry-ArtifactId: my-share-price" -H "X-Registry-Version: 1.1.1" \
    1 
    
  --data '{"type":"record","name":" p","namespace":"com.example", \
   "fields":[{"name":"symbol","type":"string"},{"name":"price","type":"string"}]}' \
    2 
    
   http://MY-REGISTRY-HOST/apis/registry/v2/groups/my-group/artifacts
    3
    Copy to Clipboard Toggle word wrap
    1
    This example adds an Avro schema artifact with an artifact ID of my-share-price and version of 1.1.1. If you do not specify a version, Apicurio Registry automatically generates a default version of 1.
    2
    MY-REGISTRY-HOST is the host name on which Apicurio Registry is deployed. For example: my-cluster-service-registry-myproject.example.com.
    3
    This example specifies a group ID of my-group in the API path. If you do not specify a unique group ID, you must specify ../groups/default in the API path.

  2. Verify that the response includes the expected JSON body to confirm that the custom artifact version was added. For example: 

    {"createdBy":"","createdOn":"2021-04-16T10:51:43+0000","modifiedBy":"",
"modifiedOn":"2021-04-16T10:51:43+0000","id":"my-share-price","version":"1.1.1",
    1 
    
"type":"AVRO","globalId":3,"state":"ENABLED","groupId":"my-group","contentId":3}
    2
    Copy to Clipboard Toggle word wrap
    1
    A custom version of 1.1.1 was specified when adding the artifact.
    2
    This was the third artifact added to the registry, so the global ID and content ID have a value of 3.

  3. Retrieve the artifact content from the registry using its artifact ID and version in the API path. In this example, the specified ID is my-share-price and the version is 1.1.1: 

    $ curl http://MY-REGISTRY-URL/apis/registry/v2/groups/my-group/artifacts/my-share-price/versions/1.1.1 \
{"type":"record","name":"price","namespace":"com.example", \
  "fields":[{"name":"symbol","type":"string"},{"name":"price","type":"string"}]}
    Copy to Clipboard Toggle word wrap

This section shows a simple curl-based example of using the registry v2 core REST API to export and import existing registry data in .zip format from one Apicurio Registry instance to another. For example, this is useful when migrating or upgrading from one Apicurio Registry v2.x instance to another.

Prerequisites

  • Apicurio Registry must be installed and running in your environment.

Procedure

  1. Export the registry data from your existing source Apicurio Registry instance: 

    $ curl http://MY-REGISTRY-HOST/apis/registry/v2/admin/export \
  --output my-registry-data.zip
    Copy to Clipboard Toggle word wrap

    MY-REGISTRY-HOST is the host name on which the source Apicurio Registry is deployed. For example: my-cluster-source-registry-myproject.example.com.

  2. Import the registry data into your target Apicurio Registry instance: 

    $ curl -X POST "http://MY-REGISTRY-HOST/apis/registry/v2/admin/import" \
  -H "Content-Type: application/zip" --data-binary @my-registry-data.zip
    Copy to Clipboard Toggle word wrap

    MY-REGISTRY-HOST is the host name on which the target Apicurio Registry is deployed. For example: my-cluster-target-registry-myproject.example.com.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat