# Disabling DELETE API **URL:** \ **Category:** Elasticsearch\ **Created:** [July 30, 2019, 6:26am UTC](https://discuss.elastic.co/t/disabling-delete-api/192830 "2019-07-30T06:26:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![tonyl](https://avatars.discourse-cdn.com/v4/letter/t/6a8cbe/32.png) [@tonyl](https://discuss.elastic.co/u/tonyl)\ **Post date:** [July 30, 2019, 6:26am UTC](https://discuss.elastic.co/t/disabling-delete-api/192830/1 "2019-07-30T06:26:51Z")
Read from the below linked post from 2014 that the DELETE method cannot be disabled in Elastic Search. > [@How to disable DELETE API](https://discuss.elastic.co/t/how-to-disable-delete-api/18867): > > Hi I'm trying to disable DELETE API option from sense or via HTTP and was not able to do it . My requirement is make DELETE API not available so that user will not accidentally delete any index . I tried the following in .yml file and restarted the server ,but still i'm able to DELETE any index .Is there something i'm missing ? Access-Control-Allow-Methods: OPTIONS, POST, GET, PUT Access-Control-Allow-Headers: X-Requested-With, Content-Type, Content-Length -- You received this message b… Like to confirm if this is still so currently? If so, is there any official documentation which states this in writing? Thanks ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [July 30, 2019, 6:52am UTC](https://discuss.elastic.co/t/disabling-delete-api/192830/2 "2019-07-30T06:52:31Z")
No, there's no docs that list all the things that Elasticsearch doesn't yet do 😉 Blocking individual HTTP methods would be unhelpful as each method, including the `DELETE` method, is used for many things. For instance, the [clear scroll API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-scroll.html#_clear_scroll_api) uses a `DELETE` request to release resources used by a long-running scroll search. Also you can bypass such a filter by using a transport client instead of a HTTP client. If you want to restrict certain actions, the best way is to use [security](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-security.html) as this is much more fine-grained and cannot be bypassed by using an alternative client. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 27, 2019, 7:00am UTC](https://discuss.elastic.co/t/disabling-delete-api/192830/3 "2019-08-27T07:00:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.