Migrating existing v2 API application to v3 OAuth2

Developer
1

Introduction

Bluescape v2 APIs are being decommissioned in 2023. All v2 APIs will lose support, and all requests sent to v2 endpoints will fail once decommissioning is complete. Visit our v3 API documentation to familiarize yourself with details on v3 API use.

We have updated our OAuth2 flows from v2 to v3. Following the process below generates updated v3 tokens.

It is very simple to migrate existing applications found under “My Applications” on your user profile page. You can use your existing application clientId and clientSecret, but you must update both the OAuth Authorization Url and the Authorization Token endpoints.

We now require you use the following scope input argument for the Authorization call:

    //mandatory for v3
    const client_scope = "scope=v2legacy offline_access";

Old v2 endpoints

OAuth Authorization URL:
https://api.apps.us.bluescape.com/authorize

Authorization Token endpoint:
https://identity-api.apps.us.bluescape.com/api/v2/oauth2/token

New v3 endpoints:

OAuth Authorization URL:
https://api.apps.us.bluescape.com/v3/oauth2/authorize

Authorization Token endpoint:
https://api.apps.us.bluescape.com/v3/oauth2/token

For example:

const base_API = "api.apps.us.bluescape.com";
const base_auth_url = `https://${base_API}/v3/oauth2/authorize`;
const token_endpoint = `https://${base_API}/v3/oauth2/token`;
const client_scope = "scope=v2legacy offline_access";

Where to Next?

Not what you were looking for? Reply below or Search the community and discover more Bluescape.