---
type: api
title: Delete data stream lifecycles
description: Removes the data stream lifecycle from a data stream, rendering it not managed by the data stream lifecycle.
url: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/operation/operation-indices-delete-data-lifecycle
resource: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/operation/operation-indices-delete-data-lifecycle
products:
  - Elasticsearch
---

# Delete data stream lifecycles

Availability: Generally available since 8.11

## Paths

- `DELETE` `/_data_stream/{name}/_lifecycle`

#### Path parameters

- `name` (union string | string[]) — required
  A comma-separated list of data streams of which the data stream lifecycle will be deleted.
Use `*` to get all data streams

## Description

Removes the data stream lifecycle from a data stream, rendering it not managed by the data stream lifecycle.

[About data stream lifecycle](https://www.elastic.co/docs/manage-data/lifecycle/data-stream)

## Required authorization

- Index privileges: `manage_data_stream_lifecycle`

## 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)

## Query string parameters

- `expand_wildcards` (string · default: open) — optional
  Whether wildcard expressions should get expanded to open or closed indices (default: open)

Supported values include:
  - `all`: Match any data stream or index, including hidden ones.
  - `open`: Match open, non-hidden indices. Also matches any non-hidden data stream.
  - `closed`: Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed.
  - `hidden`: Match hidden data streams and hidden indices. Must be combined with `open`, `closed`, or `both`.
  - `none`: Wildcard expressions are not accepted.
  Values: `all`, `open`, `closed`, `hidden`, `none`
- `master_timeout` (string · default: 30s) — optional
  The period to wait for a connection to the master node.
- `timeout` (string · default: 30s) — optional
  The period to wait for a response.

## 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 _data_stream/my-data-stream/_lifecycle
```

#### JavaScript

```javascript
const response = await client.indices.deleteDataLifecycle({
  name: "my-data-stream",
});
```

#### Python

```python
resp = client.indices.delete_data_lifecycle(
    name="my-data-stream",
)
```

#### curl

```curl
curl -X DELETE "$ELASTICSEARCH_URL/_data_stream/my-data-stream/_lifecycle" \
  -H "Authorization: ApiKey $ELASTIC_API_KEY"
```

#### Java

```java
client.indices().deleteDataLifecycle(d -> d
    .name("my-data-stream")
);
```

#### C#

```c#
var response = await client.Indices.DeleteDataLifecycleAsync(name: new[] { "my-data-stream" });
```

#### PHP

```php
$resp = $client->indices()->deleteDataLifecycle([
    "name" => "my-data-stream",
]);
```

#### Ruby

```ruby
response = client.indices.delete_data_lifecycle(
  name: "my-data-stream"
)
```

## Response examples

#### Indices delete data lifecycle response example1

A successful response for deleting a data stream lifecycle.

```json
{
  "acknowledged": true
}
```