> For the complete documentation index, see [llms.txt](https://api.clearinghouse.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.clearinghouse.net/api-reference-v2/new-features/query-behavior.md).

# Query Behavior

API v2.0 supports flexible query parameters so you can filter and retrieve exactly the records you need.

## Filtering

You can retrieve resources, documents, and dockets associated with a specific case by including the case parameter in your request. For example:

* **Filter cases by type:** `/api/v2/case/?case_type=5039`
* **Filter resources associated with a specific case:** `/api/v2/resources/?case=15150`

**Note: You cannot filter records without specifying a case. For example:** `/api/v2/documents/?document_status=Approved` Will return

```json
{"detail": "The 'case' query parameter is required."}
```

When accessing the URL endpoints for resources, documents, or dockets, please refer to these pages for detailed response examples:

* [Documents](/api-reference-v2/objects/document.md)
* [Resources](/api-reference-v2/objects/resource.md)
* [Dockets](/api-reference-v2/objects/docket.md)


---

# 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://api.clearinghouse.net/api-reference-v2/new-features/query-behavior.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.