Getting API Access

Most of the APIs provided by Scope3 are restricted to customers with a valid API key. To obtain access please reach out to your Scope3 point of contact. In the future Scope3 will provide mechanisms for customers to manage their own Access Tokens.

Access Tokens

Access tokens allow automated systems and applications to authenticate and access the Scope3 API. These tokens are generated by Scope3 and are of the format scope3_accessClientId_accessClientSecret.

Scope3 expects this value to be passed as HTTP headers on every request.

Example HTTP Request

curl --request POST 
     --url https://api.scope3.com/v2/measure 
     --header 'accept: application/json' 
     --header 'authorization: Bearer scope3_accessClientId_accessClientSecret'
     --header 'content-type: application/json' 

Updating a V1 API token for use with V2

You can create a v2 access token with your v1 credentials by combining your existing accessClientId and accessClientSecret in the following format scope3_accessClientId_accessClientSecret.

Taking a specific example where your accessClientId was l3gjkul53te and accessClientSecret was cC5ytfk6Gb9naLlPvXuI912Y9WijC1fZXHZKV6dIefRCOE9bbxjmK.

Your final key will then look something like the following:
scope3_l3gjkul53te_cC5ytfk6Gb9naLlPvXuI912Y9WijC1fZXHZKV6dIefRCOE9bbxjmK(not a working key)