> For the complete documentation index, see [llms.txt](https://developers.gurupay.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gurupay.eu/getting-started/api-concepts/filtering.md).

# Filtering

Guru Pay API endpoints (e.g., transactions api) allow you to filter results using query parameters. Filtering helps you retrieve only the relevant data for your use case (e.g., transactions within a specific date range or by type).

## Common Filter Parameters

| Parameter  | Type | Description                                             |
| ---------- | ---- | ------------------------------------------------------- |
| date\_from | date | Start date for filtering results. Format: `YYYY-MM-DD`. |
| date\_to   | date | End date for filtering results. Format: `YYYY-MM-DD`.   |

## Example Usage

**Get all completed outgoing transactions in April 2025**

```http
GET /api/v1/transactions
?date_from=2025-04-01
&date_to=2025-04-30
&type=outgoing
&status=processed

Authorization: Bearer YOUR_API_TOKEN
```

## Behavior Notes

* All filters are **case-sensitive** unless otherwise specified.
* Combime multiple filters to narrow down results.
* You may receive an HTTP 422 error if you pass invalid or unsupported filters to an endpoint.


---

# 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://developers.gurupay.eu/getting-started/api-concepts/filtering.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.
