---
type: api
title: Delete auto-follow patterns
description: Delete a collection of cross-cluster replication auto-follow patterns.
url: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-ccr-delete-auto-follow-pattern
resource: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/v9/operation/operation-ccr-delete-auto-follow-pattern
products:
  - Elasticsearch
---

# Delete auto-follow patterns

Availability: Generally available since 6.5

## Paths

- `DELETE` `/_ccr/auto_follow/{name}`

#### Path parameters

- `name` (string) — required
  The auto-follow pattern collection to delete.

## Description

Delete a collection of cross-cluster replication auto-follow patterns.

[More about auto-follow patterns](https://www.elastic.co/docs/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns)

## Required authorization

- Cluster privileges: `manage_ccr`

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

- `master_timeout` (string · default: 30s) — optional
  The period to wait for a connection to the master node.
If the master node is not available before the timeout expires, the request fails and returns an error.
It can also be set to `-1` to indicate that the request should never timeout.

## 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 /_ccr/auto_follow/my_auto_follow_pattern
```

#### JavaScript

```javascript
const response = await client.ccr.deleteAutoFollowPattern({
  name: "my_auto_follow_pattern",
});
```

#### Python

```python
resp = client.ccr.delete_auto_follow_pattern(
    name="my_auto_follow_pattern",
)
```

#### curl

```curl
curl -X DELETE "$ELASTICSEARCH_URL/_ccr/auto_follow/my_auto_follow_pattern" \
  -H "Authorization: ApiKey $ELASTIC_API_KEY"
```

#### Java

```java
client.ccr().deleteAutoFollowPattern(d -> d
    .name("my_auto_follow_pattern")
);
```

#### C#

```c#
var response = await client.CrossClusterReplication.DeleteAutoFollowPatternAsync(name: "my_auto_follow_pattern");
```

#### PHP

```php
$resp = $client->ccr()->deleteAutoFollowPattern([
    "name" => "my_auto_follow_pattern",
]);
```

#### Ruby

```ruby
response = client.ccr.delete_auto_follow_pattern(
  name: "my_auto_follow_pattern"
)
```

## Response examples

#### Delete auto follow pattern response example1

A successful response from `DELETE /_ccr/auto_follow/my_auto_follow_pattern`, which deletes an auto-follow pattern.

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