---
type: api
title: Delete an ES|QL view
description: Deletes a stored ES|QL view.
url: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-esql-delete-view
resource: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-esql-delete-view
products:
  - Elasticsearch
---

# Delete an ES|QL view

Availability: Experimental since 9.4

## Paths

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

#### Path parameters

- `name` (union string | string[]) — required
  The view name to remove.

## Description

Deletes a stored ES|QL view.

## Required authorization

- Index privileges: `delete_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)

## 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
DELETE /_query/view/NAME
```

#### curl

```curl
curl -X DELETE "${ELASTICSEARCH_URL}/_query/view/${NAME}" \
  -H "Authorization: ApiKey ${API_KEY}"
```

