Status code
Percy API uses standard HTTP success or error status codes in response. In the error scenario, we also include extra information about what went wrong encoded in the JSON response. The different HTTP status codes used in the API are listed below:
| Code | Description |
|---|---|
200 |
OK: The request was successful. |
401 |
Unauthorized: Your BrowserStack access credentials are invalid. |
403 |
Forbidden: Your credentials are valid but can’t perform this action. For example, the token type or role doesn’t allow it, or the resource belongs to a different project. |
404 |
Not Found: The requested resource could not be found. |
422 |
Unprocessable Entity: Request is well-formed but has semantic errors. The response provides more details about the error. |
429 |
Too Many Requests: You exceeded the rate limit. See Rate limits. |
5xx |
Internal Server Error: Indicates an error with the BrowserStack servers. |
Rate limits
Percy rate-limits API requests per client IP address. If you exceed a limit, the API returns 429 Too Many Requests. Read endpoints allow about 400 requests per minute.
To stay within the limits, follow these practices:
- When you receive a
429response, wait and retry with an exponentially increasing delay. - Don’t poll the same endpoint in a tight loop. To check the build status, poll at most once every few seconds.
Rate limits can change. If your integration needs a higher limit, contact BrowserStack support.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.