> ## Documentation Index
> Fetch the complete documentation index at: https://docs.willthispersonanswer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Every REST error has the same shape: an HTTP status, a code you can branch on, and a readable message.

```json 402 Payment Required theme={null}
{
  "error": {
    "code": "insufficient_credits",
    "message": "Not enough credits. 5 needed, 3 available."
  }
}
```

## Error codes

| Status | Code | Meaning |
| - | - | - |
| 400 | `invalid_request` | A missing or invalid field, a bad LinkedIn URL, or a national number with no country. |
| 401 | `invalid_api_key` | The key is missing, wrong or revoked. |
| 402 | `insufficient_credits` | Not enough credits for the whole call. Nothing was charged. |
| 404 | `not_found` | No request with that id. It may have expired or been deleted. |
| 409 | `idempotency_key_reused` | The Idempotency-Key was already used for different content. |
| 409 | `request_in_progress` | The first request with that key is still running. Retry shortly. |
| 429 | `rate_limit_exceeded` | More than 60 requests in 60 seconds. |
| 500 | `internal_error` | Something went wrong on our side. Nothing was charged. |
| 503 | `temporarily_unavailable` | Find Mobile could not run right now. Nothing was charged. Try again. |

## Not an error: unable to check

A number we could not check comes back as a normal `200` with `status: "unable_to_check"`, a reason and whether a retry can help. It is free. See [Check Number](https://docs.willthispersonanswer.com/api-reference/check-number.md#when-a-number-cant-be-checked).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.