API Deprecation & Sunset Policy

To keep our platform healthy and future-ready, we sometimes have to say goodbye to old endpoints, old features or old properties.
Think of it like spring cleaning for our API — out with the outdated, in with the improved! 🧹✨

Next Cleanup: Saturday, 28 February 2026

Why Deprecate?

When we introduce a new version of an endpoint, we promise to keep the older version running for a while.
This gives you — our awesome integrators — the time and space to migrate smoothly, without stress or surprise.

But we can’t keep every version around forever. That’s where deprecation comes in.

What Does "Deprecated" Actually Mean?

Good question! A deprecated endpoint is like an old favorite hoodie — still usable, but a bit worn and not getting any love anymore.
Here's what it means for you:

✅ It still works (for now).
🛠️ It’s no longer actively developed.
⏳ It has an expiration date.
📦 You should plan to replace it with the newer version.

Our Sunset Schedule

We like routines — and you probably do too. That’s why we’re introducing a fixed deprecation cycle:

Minimum grace period: 6 months
Goodbye days (a.k.a. sunset dates):
🗓️ 28 February and 31 August

These dates avoid end-of-year chaos and under-the-sun holiday lulls. You can set your watch (or at least your project calendar) by them!

Pro Tips for a Smooth Ride

📰 Follow our changelog for early warnings.
🦺 Check our migration guide
🧼 Build in deprecation checks or warnings in your integrations.
🗓️ Plan your migrations around our fixed sunset dates.

Stay modern. Stay clean. And keep those APIs happy!

Need Help?

Got questions? Feeling nostalgic about a deprecated endpoint?
Reach out to our support squad — we’re here to guide you safely to the other side.