> For the complete documentation index, see [llms.txt](https://documentation.rubilink.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rubilink.io/api-reference/face-image-error-responses.md).

# Face Image Error Responses

Types and causes of error responses when uploading face images to the Lapis eKYC API

***Error Responses:***

* If the provided API key is invalid, the following error message will be returned. Please ensure that the API key you provide is correct and valid.

`Response status`: **401**

```json
{
    "error": "invalid api key"
}
```

* If an invalid image URL is provided, the following error message will be returned. Please ensure that the image URL you provide is correct and accessible.

`Response status`: **400**

```json
{
    "error": "invalid face image provided"
}
```

* If an invalid image base64 is provided, the following error message will be returned. Please ensure that the image base64 is type of png or jpeg.

`Response status`: **400**

```json
{
    "error": "invalid base64 front image provided"
}
```

* If two types of image provided for face image (URL and base64), the following error message will be returned.

`Response status`: **400**

```json
{
    "error": "only one face image is accepted!"
}
```

* If size of base64 image exceeds 30mb, the following error message will be returned.

`Response status`: **413**

```
Request Entity Too Large
```

* If no document verification session is found with the provided ID, the following error message will be returned indicating that no matching session was found for the given ID.

`Response status`: **400**

```json
{
    "error": "There is no document identification data with the provided id!"
}
```

* If the provided face image does not match with the face in the document, the following error message will be returned to notify you of the mismatch between the two.

`Response status`: **400**

```json
{
    "error": "Face match verification FAILED!"
}
```