Status Codes
RealtyAPI uses standard HTTP status codes to indicate the success or failure of API requests.
Quick Reference
| Code | Name |
|---|---|
| 200 | OK |
| 400 | Bad Request |
| 401 | Unauthorized |
| 403 | Forbidden |
| 404 | Not Found |
| 429 | Too Many Requests |
| 500 | Internal Server Error |
| 502 | Bad Gateway |
| 503 | Service Unavailable |
Detailed Breakdown
The request was successful and the response contains the requested data.
{ "success": true, "data": { ... } }The request was malformed or missing required parameters.
{ "error": "Missing required parameter: address" }The API key is missing, invalid, or expired.
{ "error": "Invalid API key" }The API key does not have permission to access this resource.
{ "error": "Access denied to this endpoint" }The requested resource could not be found.
{ "error": "Property not found" }You have exceeded the rate limit. Wait before making more requests.
{ "error": "Rate limit exceeded", "retryAfter": 60 }An unexpected error occurred on our servers. Please try again later.
{ "error": "Internal server error" }The upstream service is temporarily unavailable.
{ "error": "Service temporarily unavailable" }The service is undergoing maintenance or is temporarily overloaded.
{ "error": "Service unavailable" }Error Handling Best Practices
Check the status code first
Always check the HTTP status code before processing the response body.
Parse error messages
The response body will contain a detailed error message explaining what went wrong.
Implement retry logic
For 5xx errors, implement exponential backoff and retry the request.
Handle 429 gracefully
If rate limited, check the Retry-After header and wait before retrying.
Log errors for debugging
Log error responses to help diagnose issues in your integration.