2026-08-26

📘

Late notice

These changes shipped to production in the 2026-08-26 release but were not announced at the time. They are recorded here for completeness.

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:

BeforeAfter
?nameExact=checkout?filter=label == "checkout"
?nameSubstring=checkout?filter=label.matches("checkout")

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.