Migrate from v1 to v2

Now that the Miro Developer Platform 2.0 has launched to General Availability, it is the recommended platform for all new application development. Consequently, we plan to sunset the v1 platform at the end of 2022. If your app currently uses v1, it’s time to plan your migration to v2.

To help developers migrate their existing applications from v1, we have created the following resources:

  • Web SDK
    • Comparison Guide – a walkthrough of the major changes of the Web SDK and usage examples
    • Reference Guide – a full mapping of each Web SDK v1 endpoint and its equivalent in v2
  • REST API
    • Comparison Guide – a walkthrough of the major changes of the REST API, including an overview of the new object structures
    • Reference Guide – a full mapping of each REST API v1 endpoint and its equivalent in v2, including the request type, the endpoint URL, the headers required, and example payloads

Feature Parity

For the initial launch of the Developer Platform v2, we have focused on delivering the features needed to support the development of high quality integrations. As a result, there are some features in v1 that are not yet available in v2, and a number of new features that are unique to v2. A full list of v1 features and their v2 counterparts can be found in the reference guides.

We plan to continue closing this gap until the majority of v1 features are available. In some cases, we may choose not to bring a v1 feature to v2 if that feature has low usage or conflicts with our future plans. Each instance should be explained in the reference guide, but if you have any questions or concerns, please post them in our community forum.


Did this page help you?