After resource owners are authenticated and granted access, they can exchange the authorization code for an access and a refresh token. Each token is associated with a single user (also called a subscriber) and a single application that wants to access protected resources in IBM Connections ...

The authorization check is a browser based operation in which resource owners log in and grant application access to their IBM Connections Cloud™ data.

Learn how IBM Connections Cloud™ supports Open Authorization (OAuth) 2.0.

After the original access token expires, resource owners can use their refresh tokens to get a new access token. Using the new access token, they can access the protected resources on IBM Connections Cloud™ from the application.

Each application that makes an API call must be registered with IBM Connections Cloud™. Connections Cloud registers this new application (called Internal App) and hands out the OAuth credentials. The registration is a one-time process.

Now that the access token is available, you can make the API call. Be sure to include the access token in the authorization header when you invoke the API.