Skip to main content

Deprecation policy

Arcus gives developers at least 12 months notice before removing any endpoint, field, or behavior. The deprecation lifecycle has three stages:

Response headers

When you call a deprecated endpoint or use a deprecated parameter, the response includes:
Set up alerting in your HTTP client to watch for these headers so deprecations surface before they become incidents.

Detecting deprecation headers

Current deprecations

No active deprecations. This table will be updated when the first deprecated feature is announced.

Migration guides

When a significant deprecation is announced, a migration guide will be added to the Guides section with step-by-step instructions for updating your integration.

Questions?

If a deprecation would break your integration and the timeline is too short, contact support via the in-app Help button with your use case. Arcus may be able to provide an extended sunset window for documented migration blockers.