Migrating from the V1 Measure Endpoint to Media Delivery

This guide outlines the approach to migrating your application from the V1 measure endpoint to the V2 Media Delivery Integration. The goal is to ensure a smooth transition with minimal disruptions to your service.

The Media Delivery integration offers improved scalability and integration with the CSP. See here for what's new in the latest APIs.


Key Changes

A primary consideration when migrating to Media Delivery is the transition to cloud bucket-based data transfer. To set this up, you will need to use a cloud bucket. Additionally, we have introduced a new user interface to manage cloud integrations, making the process more intuitive and streamlined.

Before proceeding, ensure you have access to the Integrate feature of the Scope3 platform.

To access the Integrate feature, click here or navigate to the Integrate tab on the left side of the UI.

If you do not have access to the Integrate feature, please contact [email protected]


Migration Steps

  1. Become familiar with the Integrate feature within the Scope3 UI. A great place to start is our walk-through videos.
  2. Ensure that you have configured a cloud bucket that Scope3 may push to and pull from as needed in your configuration. For information on how to configure cloud buckets with Scope3, click here.
    Be mindful that you have enabled correct read and write permissions for your configuration.
  3. Set up the media delivery using Integrate UI. For the full guide, see here.
  4. Push your measurement data to the cloud bucket you have configured.
  5. Confirm emissions data is successfully pushed back to your cloud bucket.
  6. Decommission your V1 integration. The Scope3 v1 API will be sunset in early 2025.

FAQ

Is there still a REST endpoint in v2?

Yes, there is a v2 measure endpoint; however, it is not recommended for production use cases because it does not deeply integrate with the CSP. It is most suitable for testing and exploring how the API works.


Support

For any additional questions or issues during the API migration process, please contact [email protected]