Merchant API deprecation policy
As our services evolve, we continuously update our APIs to introduce new features and improvements. This means that older API versions must be retired. Our API deprecation policy is designed to make this process transparent and to provide you with a clear timeline, ensuring a smooth transition to the latest API versions.
API version statuses
To keep you informed about the lifecycle of our APIs, we use the following statuses:
| Status | Description | Support |
|---|---|---|
| Active | The most up-to-date and recommended API version. Documentation is available on the launch date. | Fully supported with bug fixes and new features. |
| Deprecated | The API is scheduled for decommissioning. New integrations should not use this version. The version is marked as Deprecated in the documentation on the day of deprecation. | Supported for six months from the deprecation date (bug fixes only). |
| Decommissioned | The API is no longer available, and its documentation is removed. This status is applied six months after an API has been deprecated. | No support |
Notification schedule
We are committed to providing you with timely information about upcoming API changes. Here's how we'll keep you updated:
| Milestone | Communication channel |
|---|---|
| Deprecation date | You will be notified via email and an update in our changelog. |
| 90, 60, 30, 15, and 7 days before decommissioning | We will send reminder emails to all users of the affected endpoints. |
| Decommissioning date | A final notification will be sent via email and posted in the changelog. |
Our developer documentation will also be updated with clear labels to indicate the status of each API version. We encourage you to regularly check our changelog and keep your contact information up-to-date to ensure you receive these important notifications.