> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/filtering.md).
# Filtering
Filter ComplyCube API list responses with query parameters, supported characters, URL encoding, and endpoint-specific filters.
You can filter results returned from the API by passing them as query parameters using a standard URI format.
```
host resource
┌────────┴───────┐ ┌──┴──┐
https://api.complycube.com/v1/clients?type=company&email=example%40example.com
└─┬─┘ └┬┘ └───────────────────┬───────────────────┘
scheme API version query
```
### Supported attributes
Each endpoint provides a list of filter attributes.
{% hint style="info" %}
When multiple filters are requested, they are all applied using an **AND** operator.
{% endhint %}
Passing an incorrectly formatted filter or using an unsupported operator will return a `200` response with no results.
### Supported characters
As filters are passed as URL query string parameters, we must ensure all filters are URL safe and are strict about the characters that can be used in a filter.
Characters
Can it be used in the filter?
A-Z (upper & lower case)
Yes
0-9
Yes
$-_*.
Yes
(space)
Yes
+
Only when URL encoded (%2B)
### URL encoding filters
Some characters cannot be part of a URL (for example, space), and some other characters have a special meaning in a URL.
We recommend [URL encoding](https://en.wikipedia.org/wiki/Percent-encoding) filters to escape special characters. For example, you can encode the full filter so that `email=john.doe@example.com`would become `email=john.doe%40example.com`.
It is also recommended that you use URL building libraries to automatically encode your URLs to ensure the URLs are properly escaped before sending them to ComplyCube.
For more detail on filtering, see the **Filtering** section under each 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://docs.complycube.com/documentation/api-reference/filtering.md?ask=&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.