API changelog

2026-09-09

Version dates

None — no new API version was introduced.

Breaking changes

• Reference table {id} path parameters no longer declare format: int64. Affects GetReferenceTable, UpdateReferenceTable, UpdateReferenceTableMetadata, and DeleteReferenceTable. The parameter was and remains a JSON string on the wire, so raw HTTP callers are unaffected. Clients generated against the previous spec may have typed the parameter as a 64-bit integer.

Deprecations

None.

Migration

Regenerate your API client and treat reference table IDs as opaque strings. If your code parses or stores them as integers, change the type:

- var tableID int64 = 41007429
- client.GetReferenceTable(tableID)
+ tableID := "41007429"
+ client.GetReferenceTable(tableID)

IDs are currently numeric in appearance but are not guaranteed to remain so. Do not parse them, do arithmetic on them, or round-trip them through a numeric type — large values can lose precision in languages where the default number type is a 64-bit float.

2026-08-26

Version dates

• 2026-08-04 — the first dated API version in the public API. It currently affects GET /v1/monitors only: selecting this version returns a paginated {monitors, meta} envelope with CEL filter, limit/offset paging, orderBy, and expand, instead of the legacy bare array. The shape must be enabled for your account and returns 403 until it is. Callers that do not select a version continue to receive the legacy response, which does not change.

Breaking changes

• GET /v1/monitors — operation renamed from listMonitors to ListMonitors. Clients generated from the OpenAPI spec will see the corresponding method renamed. The HTTP method, path, parameters, and default response shape are all unchanged, so raw HTTP callers are unaffected.

Deprecations

• nameExact query parameter on GET /v1/monitors — deprecated as of version 2026-08-04. Marked deprecated: true in the spec and retained for backward compatibility. Superseded by filter.
• nameSubstring query parameter on GET /v1/monitors — deprecated as of version 2026-08-04. Marked deprecated: true and retained for backward compatibility. Superseded by filter.

No removal date has been announced for either. When a deprecated parameter is combined with filter, both conditions must match.

Migration

1. Regenerate your API client to pick up the operation rename, then update call sites:

- client.listMonitors()
+ client.ListMonitors()

Raw HTTP callers need no change.

2. Move off the deprecated name parameters at your convenience:

filter must be URL-encoded. Note that filter is only available on the 2026-08-04 shape, so this migration requires selecting that version first — until you do, keep using the deprecated parameters.

3. Select version 2026-08-04 only when you want pagination and CEL filtering. Confirm the shape is enabled for your account first; a 403 on a request that otherwise succeeds means it is not.