Having this string you are now able to exchange your application credentials for an access token by calling the Auth resource

The Authorization header of the request must include the word "Basic" followed by the Base64 encoded string. Each application is associated with an account. For more information about applications check here

Note. You can create multiple applications with different id and secret if that suits your integration case. Read more...

The body can also contain a scope parameter in order to limit the permissions of the access token. For example, if an application sends only SMS it can request only the SMS scope. By default, if the scope parameter is omitted, then the token receives all the allowed scopes of the application

Time in seconds that the token will expire. The token is set by default to expire in 1 hour (3600 seconds).

scope

The requested scopes.

permissions

The permissions granted to the authenticated application.

That's it! Now you can access all Routee services using the access_token of your application to the header of each resource!

Note. All requests made for a Routee Application are associated to the Routee Account. You can use Routee Platform to generate custom reports for all your activity.

Important!

All tokens that are issued from Routee's authorization server are valid for 1 hour. This allows better security for your HTTP calls. That means that once you get an HTTP response with a status code of 401, from any Routee API resource, you should issue a new token and repeat your previous request with the new token.

To issue a new token, you follow the same procedure of exchanging your application credentials through the authorization server.