# Errors

We use standard HTTPS error codes for the API error handling. Below is the list of error codes:

| HTTP Status Code | Title | Description | Possible causes and solution |
|  --- | --- | --- | --- |
| 400: Bad request | One or more errors occurred in the request | We cannot process the request due to something incorrect or malformed in the client's request | Verify the request model as it is invalid, and adjust it according to the error message. |
| 401: Unauthorized | Invalid authorization | Incorrect credentials | Verify the authorization header to ensure it is correct and adheres to the requirements outlined in the authentication section of the documentation. |
| 402: Payment Required | Account locked due to insufficient funds | Sinch credit balance is negative | Top up balance on Sinch Dashboard or contact your account manager. |
| 403: Forbidden | Number lookup for the requested country is disabled. | Number lookup for the requested country is disabled for your account. Please contact support for more information on enabling services for this country. | Number Lookup for Canadian numbers is only available to customers with a CLNPC license. Please refer [here](/docs/number-lookup-api-v2/overview#canada-number-lookup) for information on obtaining a license. |
| 403: Forbidden | Line type lookup feature is disabled | Line type lookup feature is disabled for this application | Enable line lookup feature for the application on Sinch Dashboard. |
| 403: Forbidden | Line type use cases not specified |  | Please refer [here](/docs/number-lookup-api-v2/overview#line-type-use-cases) for information on specifying use cases. |
| 404: not found | Number not found | Requested number not found from data set | Double check if number is correct. |
| 429: Too many requests | Rate limit exceeded |  | The default rate limit is 10 requests per second. If a higher capacity is required, please contact us. |
| 500: Internal error | Internal server error | Error occurred on server side | The error occurred on the server side. Please provide the `traceId` from the response, so we can investigate the issue further. |