## Error Codes
Lusha API uses standard HTTP response codes to indicate the status of your request.
| Status Code | Name | Description |
|  --- | --- | --- |
| **200** | OK | Successful request |
| **400** | Bad Request | Badly formatted request |
| **401** | Unauthorized | The API key is invalid |
| **402** | Payment Required | Your account requires payment |
| **403** | Forbidden | Your account is not active. Please reach out to support at *support@lusha.com* for assistance |
| **403** | Forbidden | Your pricing version does not support requesting individual datapoints [revealEmails, revealPhones] |
| **404** | Not Found | The requested endpoint was not found |
| **412** | Precondition Failed | The request failed due to invalid syntax that was provided. Please make sure to send a full name field that contains a valid first & last name |
| **429** | Too Many Requests | You've reached your trial limit, please contact support for upgrade |
| **429** | Too Many Requests | Daily API quota limit exceeded. Limit X calls per day |
| **429** | Too Many Requests | Hourly API rate limit exceeded. Limit: X calls per hour. Reset in X seconds |
| **451** | Unavailable For Legal Reasons | We are unable to process this contact request due to our GDPR regulations |
| **499** | Client Closed Request | Request failed due to request timeout |
| **5XX** | Server Error | There's a problem on Lusha's end |

**Error Response Format**
In case of an error, the response body will contain details about the error:

```json
    {
      "error": {
        "code": 400,
        "message": "Invalid request parameters"
      }
    }
```
**Handling errors**
- Always ensure your API key is correct and valid
- Pay attention to the specific error message and code to troubleshoot issues efficiently
- Implement proper error handling and retry logic in your application
- For 5XX errors, implement exponential backoff before retrying



---