Deprecations

This is the canonical list of API surfaces on a removal clock. It's the page to bookmark and check before you build on anything you're unsure about. For the policy behind it — what counts as breaking and how versioning works — see Breaking changes & versioning.

Active deprecations

Nothing is deprecated.

The API is at v1 and no endpoint, field, parameter, or event is scheduled for removal. When that changes, the affected surface appears here with its announcement date, removal date, and a migration link — and you'll get the notifications below before the entry ever lands.

How you'll be told

Every deprecation is announced through three channels, so you never learn about one only by hitting an error:

  • Changelog. A Deprecated entry when it's announced, aRemoved entry when it's gone. Subscribe to thechangelog.
  • Email. To your Organization's admins on announcement day, 30 days before removal, and on removal day.
  • Sunset header. Every response from a deprecated endpoint carries aSunset date (RFC 8594) and a Deprecation: true flag. Log it in your client to catch deprecations programmatically.

The window

You get six months between announcement and removal. The deprecated surface keeps working unchanged for that entire window — the date in the Sunset header and the changelog entry is the real cutoff. The full rationale is onBreaking changes & versioning.

Next

Read the versioning policy on Breaking changes & versioning, or check the changelog for the latest releases.