# Errors

{% hint style="info" %}
GraphQL can significantly enhance the power of your API Integration. To onboard, please reach out to your Account Manager for pricing information.
{% endhint %}

A GraphQL error is handled differently than a typical REST error.  GraphQL will always return a status code of **200 - OK**, but if an error occurs, an `errors` array will be returned in the response:

```json
{
    "errors": [
        {
            "message": "Resource Not Found.",
            "locations": [
                {
                    "line": 2,
                    "column": 5
                }
            ],
            "path": [
                "entity"
            ]
        }
    ],
    "data": {
        "entity": null
    }
}
```

In this `errors` array, you will see a collection of error objects. The error object will define a `message` - what the error was that occurred, a `location` - where in the json structure the error occurred, and a `path` - the node in the json where the error occurred. 

The response will also include any partial `data` that could be retrieved before the error occurred.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://api-docs.rightsline.com/graphql/errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.