Understanding 404 Errors When Accessing Deprecated Schema Registry Cluster Management v2 APIs

Overview

As part of Confluent’s ongoing efforts to improve platform security and performance, the Schema Registry Cluster Management v2 APIs (/srcm/v2) have been deprecated since August 2024. In preparation for decommissioning, access to these APIs has been restricted using an allow list mechanism.

What Has Changed?

Only customers who accessed the /srcm/v2 APIs between July 1 and July 15, 2025, are included on the allow list and can continue using these endpoints temporarily. Other users, including those with only occasional usage outside this period, will now encounter errors when attempting to call these APIs.

How Will This Affect Me?

If your team, scripts, or automation pipelines (such as CI/CD jobs) make requests to the /srcm/v2 endpoints and your account is not on the allow list, you will see HTTP 404 Not Found errors. These failures may happen whether you invoke APIs directly, or use tools and clients that depend on them, including:

• Confluent CLI v2
• Confluent CLI v3
• Terraform Provider v1

Why Am I Seeing 404 Not Found Errors?

A 404 error indicates that the specific API endpoint you are trying to reach is no longer accessible to your account. This is because access is now strictly controlled via the allow list as a step towards decommissioning.

Recommended Actions

To restore or maintain functionality, please follow these remediation steps:

• Upgrade your client tools and scripts:
  Move to the latest supported versions specific to the management APIs:
  • Use Confluent CLI v4 or above
  • Adopt Terraform Provider v2
  • Update API calls to target /srcm/v3 endpoints

Additional Assistance

We strongly encourage all customers to upgrade as soon as possible to ensure continued compatibility, security, and access to the latest features. If your organization requires support in planning or executing this migration, please contact Confluent Support with details about your current API usage and your migration timeline.

Summary Table

Proactive migration is the best way to avoid disruptions as Confluent completes the decommissioning of the deprecated /srcm/v2 APIs.