At Mircod, we believe in continuous development and add new features and improvements to our products regularly.
We also want developers and users of integrations with Mircod to benefit from these updates, so we want to make sure our APIs reflect them by releasing new versions. However, we know that API deprecation can cause disruption for developers, and want to minimise this as much a possible, whilst also still making new updates available to everyone so that the community can continue to innovate.
That’s why we’re now introducing a standard release schedule for our APIs, so you can always be aware of upcoming API deprecations well in advance and can move to new versions without disrupting your integration’s service.
We are currently on API V2 – the below versioning structure will come into place when V3 is introduced early next year, at which point V2 will move into ‘secondary’ state and we’ll announce the relevant dates for depreciation.
When a new API version is announced it will be the ‘current’ version for a minimum of 6 months. We will also continue to support the previous version for at least 6 months so that you have time to move to the new version, after which it will be sunset and will no longer be available.
We will never introduce breaking changes to an API version in current or secondary status; these changes will be rolled into new versions.
We strongly recommend migrating to the newest API version as soon as the one you are using moves into secondary status. We also encourage you to try out new API versions when in beta but don’t recommend using these as your primary source as they may be unstable.