> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/configuration/queries/query-platforms/odata-queries.md).

# Odata Queries

Odata v4 queries support simple, aggregation and command query types, whereas v2 supports only simple and command queries.

Odata specific features for special use cases are as follows:

## Query Parameters

<table><thead><tr><th width="267.88983220943845">Parameter</th><th width="200">Definition</th></tr></thead><tbody><tr><td>path</td><td>Service endpoint path for running the query (except for entity name, which is provided in "from" expression of the query)</td></tr></tbody></table>

## Join Parameters

<table><thead><tr><th>Parameter</th><th width="200">Definition</th></tr></thead><tbody><tr><td>option</td><td>Extra options to add to an expand() statement (v4 only)</td></tr></tbody></table>

{% hint style="info" %}
Odata v2 allows automatically joining entities without any conditions, whereas v4 allows using join conditions, which are translated into $filter statements inside expand.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.rierino.com/configuration/queries/query-platforms/odata-queries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.