REST API service limits

To ensure maximum performance for all REST API users, the REST API server enforces limits on your account's use of the API. This prevents an account from accidentally overusing the API and negatively impacting the performance of other user's REST API calls.

Bearer token expiration time

Once it is included in a response from the login  resource, the bearer token is valid for 18 hours.

REST API call limits

Each account can make a maximum of 50 calls to the API in any given five (5) minute period. This limit includes all requests issued for all bearer tokens for all users associated with the account. If you exceed this limit, the REST API server will respond to your request with a 503 status and a message in the response body similar to the following:

{user} exceeded REST API invocation limit

Test results resource limits

The Test Results resource has a few limitations to the amount of data that you can retrieve. For more information, see Test results.

Avoiding service limits

We recommended that you design your application to avoid these limits. For example, if you automatically retrieve large amounts of test data, spread the calls to the REST API over a period of time. If you do encounter a 503 status, you can design your application to automatically try the REST API call again after a period of time.

For test results, the most efficient retrieval method is to use the incremental data feed feature. When used correctly, incremental data feeds never exceed the REST API service limits.