> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/api-reference/location-api/location-error-codes.md).

# Location Error Codes

When a request fails, `status.status` returns `ERR` and the `errorCode` and `errorMessage` fields are populated.

| Code | Message                                                   | Cause                                                                                                                                            |
| ---- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| 0    | Decoding failed: Syntax error                             | The JSON is structured incorrectly. This can occur when text is pasted from Microsoft Word, because some Word characters differ from ASCII.      |
| 1    | The number of cells is 0                                  | The `mast`, `power`, or `ta` values are absent or incorrect.                                                                                     |
| 601  | Missing parameter ICCID/MSISDN                            | The ICCID or MSISDN is absent or incorrect, or the request URL uses `http` rather than `https`.                                                  |
| 602  | Unauthorised Access, Invalid Account, or Invalid Password | The username or password is incorrect, the account does not exist in Infinity Classic, or the account is not authorised to use the Location API. |
| 603  | Parameter `<parameter>` value missing                     | The named parameter is absent or incorrect. Where two parameters are interchangeable, the error refers to either one.                            |
| 605  | No msisdn found                                           | The ICCID or MSISDN is absent or incorrect, or the request URL uses `http` rather than `https`.                                                  |
| 606  | NoLookupFound                                             | The location service cannot find a latitude or longitude for the device.                                                                         |
| 611  | invalid                                                   | The ICCID or MSISDN is incorrect, or is not available from this account.                                                                         |

A response body beginning `<!DOCTYPE html>` indicates that the request URL path is incorrect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/api-reference/location-api/location-error-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.