API Documentation
Errors
Troubleshoot problems with this comprehensive breakdown of all error codes.
Client Side Error
Here is how an error response looks like.
Here is a list of all error codes Bitsy API returns:
Bad Request
- Status: 400
- Problem: The request is malformed, either missing required fields, using wrong datatypes, or being syntactically incorrect.
- Solution: Check the request and make sure it is properly formatted.
Unauthorized
- Status: 401
- Problem: The request has not been applied because it lacks valid authentication credentials for the target resource.
- Solution: Make sure you are using the correct API key or access token.
Forbidden
- Status: 403
- Problem: The server understood the request, but is refusing to fulfill it because the client lacks proper permission.
- Solution: Make sure you have the necessary permissions to access the resource.
Not Found
- Status: 404
- Problem: The server has not found anything matching the request URI.
- Solution: Check the request and make sure the resource exists.
Method Not Allowed
- Status: 405
- Problem: The HTTP method used for the request is not allowed for the specified resource.
- Solution: Check the API documentation to ensure you are using the correct HTTP method (e.g., GET, POST, PUT, DELETE) for the endpoint, and adjust your request accordingly.
Unprocessable Entity
- Status: 422
- Problem: The server was unable to process the request because it contains invalid data.
- Solution: Check the request and make sure input data is valid.
Rate Limit Exceeded
- Status: 429
- Problem: The request has been rate limited.
- Solution: Wait for a while and try again.
Server Side Error
Here is how an error response looks like.
Internal Servere Error
- Status: 500
- Problem: The server encountered an unexpected condition that prevented it from fulfilling the request.
- Solution: Try again later. If the problem persists, contact support.
Was this page helpful?