| Scenario | HTTP Status Code |
| API Call Successful, Access OK, Record Count 0 | 200 |
| API Call Successful, Access OK, Record Count 1+ | 200 |
| Validation Error / Bad Request Many of our endpoints look for at least one filter to be provided to limit the impact on the back-end data services layer. /reports is one example, that requires at least a date range or position id. | 400 |
| API Call Missing Credentials / Unauthorized Check to see if your request contains a valid access_token or refresh_token. | 401 |
| API Call Successful, Access Forbidden Permissions are missing, either in the OAuth 2 Scope, or the TrackTik web portal Employee (username and password) | 403 |
| Too many requests You've sent too many requests in the past minute and need to reduce the number for the next minute to cool things off. The limit is usually in the thousands and therefore generous, but some folks make the error of having too much parallelism or poor error trapping and passing those limits. | 429 |
| Internal Server Error TrackTik’s system is missing a validation, a database constraint wasn't respected, or other unexpected server side error. | 500 |
| Gateway Timeout Your API call took more than 30 seconds to execute and return results. Try to reduce the range of rows of data that your call is covering. Maybe add a date range, or index range. TrackTik's API is tailored as an Operations API, not for data mining nor bulk extraction. | 504 |
mobile app, shift app, logging out