Hey everyone,
We’re excited to share that we’ve shipped API versioning and lifecycle states—giving developers more control and confidence when building on the Deel API.
Until now, shipping new functionality meant asking every integration to migrate at the same time, so instead of improving endpoints, we’d create new variants and widen the integration surface.
With API versioning and lifecycle states, you can now:
-
Move at your own pace. Add
X-Version: YYYY-MM-DDto pin to a specific release. Your existing integration keeps working until you’re ready to upgrade -
Try beta features early. Use
X-Beta: trueto opt in to new functionality before it reaches stable -
Build on a published stability contract. Stable endpoints carry a minimum one-year lifecycle commitment
-
Catch deprecations before they become incidents. Retiring endpoints return a Deprecation and Sunset header with the exact removal date, at least a year in advance
Head to the API versioning guide for the full lifecycle policy, current stable version, and how to adopt new versions when you’re ready.
Already building on the Deel API? We’d love to hear how this lands for you, or what questions come up as you dig in.
- Mark and the Developer Experience team