API Deprecation Notice
As part of our ongoing efforts to improve and innovate our product offerings, we have decided to deprecate a number of API endpoints from Pleo’s API (now referred to collectively as the Legacy API). The legacy methods will be replaced by new methods over the coming months. We understand that this change may impact your current workflow, and we want to assure you that we are committed to providing the support you need during this transition. Here are the key details and dates to keep in mind:- Deprecation Date: Effective immediately, the Legacy API is considered deprecated. This means that while the API will remain operational until the end-of-life date, no new features will be added, and only critical security updates and bug fixes will be provided.
- End-of-Life Date: After this date, the API endpoints will no longer respond to requests.
- Migration Support: Once migration guides are available, they will be communicated alongside the end-of-life date so you can plan accordingly. Pleo Support will be on hand to answer any questions. Further information on the migration path for each use case is provided below.
- Action Required: If you are currently using the Legacy API, we recommend beginning the process of migrating your systems as soon as possible. Please review any integrations or applications that depend on the Legacy API and plan accordingly.
Migration Plans
If your implementation of the Pleo API is for any of the following use cases, find more information about how these functions will be supported going forward.Accounting Export
Exporting Pleo expenses into your accounting or ERP system.User Management
Synchonising with your HR system to automate the adding or removal of user from PleoProject Management
Ensuring that cost centres within your project management software are represented in Pleo to easily reconcile expenses.Company Balance
If you are customer, please direct any questions to your support contact. If you are a partner, you can email api@pleo.io.