# Create view

> Creates a saved view: a named filter and sort over people. Filter conditions are combined with AND. Returns 400 validation error with INVALID REQUEST BODY…

`POST /v2/api/crm/views`

<Note>
**Required scope:** `CRM_WRITE`
</Note>

## Body fields

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `name` | string | yes | Display name, up to 255 characters |
| `filters` | array | no | `{ field, operator, value }` conditions, combined with AND. Up to 50 |
| `sort` | array | no | Up to 2 `{ field, order }` entries. `order` is `asc` or `desc`. `field` is a sortable built-in field (`name`, `company`, `job_title`, `website`, `created_at`, `updated_at`, `last_activity`) or the `key` of a sortable custom field from [List custom fields](/docs/crm/list-attributes) |
| `owner_type` | string | no | `USER` (default, private to you) or `TEAM` (shared with your team) |

```json
{
  "name": "Hot leads",
  "filters": [
    {
      "field": "company",
      "operator": "CONTAINS",
      "value": "Acme"
    }
  ],
  "sort": [
    {
      "field": "created_at",
      "order": "desc"
    }
  ],
  "owner_type": "USER"
}
```

See [Filters](/docs/crm/views-overview#filters) for the fields and operators you can use.

## Response

Returns `201` with the view.

```json
{
  "data": {
    "id": "cvw_2abc",
    "name": "Hot leads",
    "filters": [
      {
        "field": "company",
        "operator": "CONTAINS",
        "value": "Acme"
      }
    ],
    "sort": [
      {
        "field": "created_at",
        "order": "desc"
      }
    ],
    "owner_type": "USER",
    "user_id": "usr_2abc",
    "team_id": null,
    "created_at": "2026-10-23T10:00:00",
    "updated_at": "2026-10-23T10:00:00"
  }
}
```

## Errors

| Status | Code | When |
|--------|------|------|
| `400` | `INVALID_REQUEST_BODY` | `name` is missing, blank or longer than 255 characters, `filters` has more than 50 entries, or `owner_type` is not `USER` or `TEAM`. Field-level problems are listed in `errors[]` with the `field` (`name` or `filters`) |
| `400` | `INVALID_FILTER_FIELD` | A filter `field` is neither a built-in person field nor the `key` of a custom field from `GET /v2/api/crm/attributes`. `param` is `filters` |
| `400` | `INVALID_FILTER_OPERATOR` | A filter `operator` does not match the type of its field. The message names the field. `param` is `filters` |
| `400` | `INVALID_FILTER_VALUE` | A filter `value` cannot be read for the type of its field: a number field needs a numeric value, a date field needs an ISO 8601 date such as `2026-01-31` or `2026-01-31T00:00:00Z`. The message names the value and the field. `param` is `filters` |
| `400` | `INVALID_SORT_FIELD` | A sort `field` is neither a built-in field nor a custom field `key` from `GET /v2/api/crm/attributes`. `param` is `sort` |
| `400` | `FIELD_NOT_SORTABLE` | A sort `field` exists but cannot be sorted on. Use a built-in sortable field or a sortable custom field. `param` is `sort` |
| `400` | `USER_HAS_NO_TEAM` | `owner_type` is `TEAM` but you do not belong to a team. Use `USER`. `param` is `owner_type` |
| `403` | `API_KEY_INSUFFICIENT_SCOPE` | The key does not hold `CRM_WRITE` |
