Tangoe Mobile REST API

Authentication is a token-based endpoint that will generate a JWT access token valid for 30 minutes. Input is Client ID, Client secret of respective business and email address of the user.

Link to token endpoint: https://anypoint.mulesoft.com/exchange/portals/tangoe/f5574299-614a-4d3f-885d-24958c10613f/mobile-v3-api/minor/2.0/console/method/%2329/

Method: POST
Example Endpoint: https://{{subdomain}}.thefutureis.mobi/v2/token

Example JSON Body:

{
"client_id": "tangoe to provide",
"client_secret": "tangoe to provide",
"subject": "tangoe_api@{subdomain}.com",
"grant_type": "client_credentials"
}

Response data points:

{
"access_token": " ",
"token_type": "bearer",
"expires_at": 1725003472,
"audience": " ",
"scope": "user"
}

Pagination

By default, collections are paginated with pages having 100 items. If you wish to return a different number of items add the per_page parameter. Per page must be less than 1,000. By default, the first page is returned. To return another page, add the page parameter set to the integer value of the page of results you wish to be returned.

Rate Limiting

GET requests are limited to 100 per minute. Once the rate limit threshold is met, an HTTP status code of 429 (Too Many Requests) will be issued.

Tangoe Mobile Environments

The two Tangoe environments our clients can leverage.

1. Production -> Where the clients' user data will be populated.
2. Stage -> Where the client will develop and test using their actual data mirrored from production.