---
type: api
title: Create or update an ES|QL view
description: ## Required authorization
url: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-esql-put-view
resource: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-esql-put-view
products:
  - Elasticsearch
---

# Create or update an ES|QL view

Availability: Experimental since 9.4

## Paths

- `PUT` `/_query/view/{name}`

#### Path parameters

- `name` (string) — required
  The view name to create or update.

## Required authorization

- Index privileges: `create_view`

## Authentication

- Api key: `Authorization: <value>`
  Elasticsearch APIs support key-based authentication.
  You must create an API key and use the encoded value in the request header.
  For example:
  
  
  ```
  curl -X GET "${ES_URL}/_cat/indices?v=true" \
    -H "Authorization: ApiKey ${API_KEY}"
  ```
  
  To get API keys, use the `/_security/api_key` APIs.
- Basic: `Authorization: Basic <credentials>`
- Bearer: `Authorization: Bearer <token>`
  Elasticsearch APIs support the use of bearer tokens in the `Authorization` HTTP header to authenticate with the API.
  For examples, refer to [Token-based authentication services](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/token-based-authentication-services)

## Request body

`application/json`

- `query` (string) — required
  The ES|QL query string from which to create a view.

## Response

`application/json`

- `acknowledged` (boolean)
  For a successful response, this value is always true. On failure, an exception is returned instead.
## Code examples

#### Console

```console
PUT /_query/view/NAME
{
  "query": "string"
}
```

#### curl

```curl
curl -X PUT "${ELASTICSEARCH_URL}/_query/view/${NAME}" \
  -H "Authorization: ApiKey ${API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "string"
  }'
```