Tangoe Procurement for Rivermine and Command [MobProc]

NOTE: This tutorial assumes that you are using a client ID and client secret for an API client application that is configured to allow Refresh Token as one of its Allowed Grant Types__ configured in PingFederate.

The following information is required to refresh an access token:

• client_id: Client ID assigned to your API client application.
• client_secret: Client secret assigned to your API client application.
• scope: OAuth scope(s) required for the API you are using.
• refresh_token: The refresh token that was obtained when the access token was created.

Endpoints

An access token is refreshed by making an HTTP POST to our Ping authentication endpoint. The specific endpoint used will depend upon your instance’s environment type:

• For Production: https://oauth.tangoe.com/as/token.oauth2
• For QA: https://oauthqa.tangoe.com/as/token.oauth2

NOTE: Although a unique client ID/client secret pair can be used to access multiple APIs, they are always assigned per environment. Therefore, an client ID/secret pair that is valid for one environment will not work for another environment.

Request Query Parameters

To refresh an access token, the following query parameters need to be passed with this POST request:

Example

The following is an example of a POST request to get a token:

https://oauthqa.tangoe.com/as/token.oauth2?grant_type=refresh_token=376af94124f4400e9227c89937c12354=81f40d2777ea4a41A992535F17AC92EC=MOBPROC=a9AhNvcffquYkV4bSw0O6gt4gKZRvTUGR2lfR8nJf4

The following is an example of a response that might be returned:

{
   "token_type": "Bearer",
   "expires_in": 7200,
   "refresh_token": "wBzXpMnRjAyiLMDrn0vmhnO89pMbm22WJVXuf0RazH",
   "access_token": "Ql0mwXlo8lWHmczeiopaDt5rLMTO"
 }

The following properties are returned in the newly-refreshed access token response: