Troubleshooting Errors

Learn how to diagnose and resolve common problems for the REST API.

400 Bad Request

These errors indicate that there is a problem with the format of your request.

The response should have some details about the problematic part of your request, for example:

  "code": 400,
  "message": "malformed request, \"hello\" cannot be converted to valid RFC3339 timestamp"

401 Unauthorized or 403 Fordbidden

These errors indicate that you don't have permission to make the request.

Common reasons for this error are an expired access token (JWT) or not having the required scopes to access the path.

Please make sure you review Authentication.

404 Not Found

This error indicates that the requested resource does not exist.
If you are requesting a specific record, for example /v1/manager-reviews/1db82ba3-cc1d-11ed-9e57-022c08614d88, double check that the ID is correct.
Otherwise, make sure that the request path is correct.

429 Too Many Requests

This error indicate that you have hit our rate limits, please head to Usage Limits for more information.

503 Service Unavailable

If it takes more than 15 seconds to process an API request, we will terminate it and you will receive a 503 Service Unavailable with "timeout" body. If so, please give it a minute and retry your request. If you are encountering repeated timeouts, please reach out to us.

Another possible cause for a 503 is that you have hit our rate limits, please head to Usage Limits for more information.

5XX Family of Errors

If you encounter repeated errors in the 5XX family (e.g. 500 or 502), it's possible that we are having issues in the platform. If that's the case, we will publish
an outage in this documentation portal and work on a fix as soon as possible. Don't hesitate to reach out to us.

Other errors

If you observe an error that is not included here, you should refer to the status code and message that the API gives you. Most errors will provide a clue about what is wrong.