RouteLink API v2.0: How Do I Submit a Refresh Token Request?

Refresh Token Request

Each RouteLink Client token has an associated expiration date. Once the token expires, the token will be rejected by RouteLink. The following is an example REST/JSON refresh token request:

 GET /routelink/v2/refreshToken HTTPS/1.1

Authorization: Bearer c0d97b52-35d9-32c2-a37d-6126a186a844

 Please Note: The token inside the request is the "old" token about to expire (the one you are asking to refresh). This command fails if your token has already expired. If that happens, you must manually use the RouteLink website to acquire a new token or alternatively you can use the ‘/sessionOpen’ API.

Refresh Token Response

The response to a refresh token request contains the new token. Upon receiving the response, the old token is invalid and only the new token can be used for any future API requests.

 The following is an example JSON token refresh response from RouteLink:

{

"token":

    "c0d97b52-35d9-32c2-a37d-6126a186a844",

"expiration":"01/09/2017 15:56:21"      // always in GMT

}