# invalid_operator

Source: https://capacms.com/docs/errors/invalid_operator

400 invalid_request. The filter or sort uses an operator this field type does not support.

| HTTP status | `type`            | Surfaces      |
| ----------- | ----------------- | ------------- |
| 400         | `invalid_request` | REST, GraphQL |

## What it means

The filter or sort uses an operator this field type does not support.

| When                                                                 | What the `hint` tells you                                |
| -------------------------------------------------------------------- | -------------------------------------------------------- |
| an operator the type does not take, or an unsortable field in `sort` | the operators that type does take, or the sortable types |

## What to do

Use one of the operators the hint lists for that field.

## On GraphQL

`/api/graphql` answers the same `code` inside `errors[].extensions`. The status depends on the `Accept` header you send ([status codes](https://capacms.com/docs/api/graphql#status-codes)):

| `application/json` | `graphql-response+json` | When                                                                                                                                                                                                             |
| ------------------ | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 200                | 400                     | REST planner refusals, with `path` set to the root field. `invalid_select` also refuses one relation list read twice in an entry with different arguments (see [Not built yet](https://capacms.com/docs/api/graphql#not-built-yet)) |

## See also

* [Filtering](https://capacms.com/docs/api/entries#filtering)
* [Sorting](https://capacms.com/docs/api/entries#sorting)