# Search data

Schema: #/components/schemas/search_request

Method: SCHEMA
Version: 2.7
Security: bearerAuth

## Schema fields:

  - `query` (any, required)

  - `query.field` (string)
    The accepted field that you want to search on.
    Example: created_at

  - `query.operator` (string)
    The accepted operators you can use to define how you want to search for the value. Operator support depends on the field's data type. The breakdown below is for Contacts search; the other search endpoints that share this schema accept a different set per field:
- `string`
 fields:
`=`
,
`!=`
,
`IN`
,
`NIN`
,
`~`
,
`!~`
,
`^`
,
`$`
- `tag_id`
:
`=`
 and
`!=`
 only. Every other operator returns an error.
- `boolean`
 fields:
`=`
,
`!=`
,
`IN`
,
`NIN`
- `integer`
 fields:
`=`
,
`!=`
,
`IN`
,
`NIN`
,
`<`
,
`>`
,
`<=`
,
`>=`
- `date`
 fields (all standard timestamp attributes and date custom attributes):
`=`
,
`<`
,
`>`
 only.
`!=`
,
`<=`
,
`>=`
,
`IN`
, and
`NIN`
 are not supported and return an error.
    Enum: "=", "!=", "IN", "NIN", "<", "<=", ">", ">=", "~", "!~", "^", "$"

  - `query.value` (string)
    The value that you want to search on.
    Example: 73732934

  - `query.operator` (string)
    An operator to allow boolean inspection between multiple fields.
    Enum: "AND", "OR"

  - `query.value` (any)

  - `pagination` (object)

  - `pagination.per_page` (integer)
    The number of results to fetch per page.
    Example: 2

  - `pagination.starting_after` (string)
    The cursor to use in the next request to get the next page of results.
    Example: your-cursor-from-response

