Removal notice: API v1.1beta1

In the coming days or weeks we will remove the v1.1beta1 API. Calls against the v1.1beta1 API, will be rerouted to v1.1beta2 instead. Review the  API v1.1beta2 release notes to understand if you are affected by any of the breaking changes between 1.1beta1 and 1.1beta2.

Who is affected?

We expect most customers to be unaffected by this change.

Based on our metrics, we do not expect any customers to be affected for thier frequently used code (such as data inserts). However, infrequently used code, such as management scripts or similar, may have eluded our telemetry data, where we keep a strict and limited history. Such code may need updates before it's next usage if either of the following is true:

• You rely on PyClarify v0.3.x
• You write your own HTTP calls.

How to update?

For those who use PyClarify

PyClarify 0.3.x versions are known to use v1.1beta1, while PyClarify 0.4.x versions are known to use v1.1beta2. To rely on a stable API verison, we recommend updatig to v0.5.0 or later. Because old versions may contain bugs, the best recommendation, is to update to the latest version of PyClarify.

For those who use Claify-Go

The Clarify SDK never used API v1.1beta1, and is thus not affected. However, versions between v0.2.3 and v0.2.6 uses API v1.1beta2. We recommend using v0.3.0 or later, which uses API v1.1.

For those who use the Node-RED Clarify node

The Node-RED plugin only relies on stable APIs (v1.0 or v1.1). However, there may be bug fixes or performance improvements in newer versions, making a upgrade worthwhile if you experience issues.

For those that uses the Telegraf Clarify Output Plugin

The upstream version of Telegraf is relying on clarify-go v0.4.1, as of June 2026. This version is not affected by the removal of API v1.1beta1.

For those who write their own HTTP calls

Everyone writing their own HTTP calls and specify the header X-API-Version: 1.1beta1 should update their to use X-API-Version: 1.1. Review 1.1beta2 and 1.1 release notes to understand required code changes.

For those who use MQTT ingestion

Not affected; MQTT does not use HTTP version selection.

Using stable v.s. beta API versions

In general, users are recommended to always use a stable API when possible. Usage of API pre-release APIs (v1.1beta1 and v1.1beta2) should be updated to use API v1.1 instead. This is because our pre-releases are not covered by our bacwards compatibility promise.

Usage of API v1.0 remains safe, and doesn't need any updates.

Usage of API v1.2alpha1 should be updated to API v1.2 as soon as that version is released. A new final release of this version is expected in September 2026.

Stable APIs in SDKs

When using one of our SDKs, it's usually out of your control to decide if you shoud use a stable or pre-release version for our method calls. However, we are aware of this limitaitons, and are taking precations to limit impact on customers.

Newer SDK code typically don't include pre-release methods in their main client, but expose a separate experimental client or similar to allow access to pre-released methods. Use of this experimental code may break.

For some older SDK code, we have included some pre-release API calls in the main client methods. For such code, we are more commited to keeping the particular call pattern for the relevant pre-release versions alive for longer.