# /\_snapshot endpoint API documentation

**URL:** <https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404>\
**Category:** Elasticsearch\
**Created:** [October 10, 2017, 3:42pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404 "2017-10-10T15:42:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SimoneCafiero](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@SimoneCafiero](https://discuss.elastic.co/u/SimoneCafiero)\
**Post date:** [October 10, 2017, 3:42pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/1 "2017-10-10T15:42:57Z")

</div>

Hi guys,  
is there a complete documentation of the following API endpoint:

- /\_snapshot

I would like to know if it's possible to edit backup metadata names (snap-CUSTOM\_NAME or meta-CUSTOM\_NAME instead of having a random String where CUSTOM\_NAME is) and eventually how to do that through any API parameter. So any documentation of that endpoint would be very helpful.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 10, 2017, 3:57pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/2 "2017-10-10T15:57:19Z")

</div>

The question is why you would like to do that?  
The files should not be used by anything else than snapshot/restore api.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [October 10, 2017, 4:06pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/3 "2017-10-10T16:06:55Z")

</div>

The short answer is no. You should only be interacting with the files in your snapshot repository through the Elasticsearch Snapshot/Restore API. You should never edit or manipulate these files directly.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [October 10, 2017, 4:12pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/4 "2017-10-10T16:12:53Z")

</div>

Hahaha, @dadoonet! I swear your response wasn't there when I clicked "reply."

---

<div class="post-metadata">

**Author:** ![SimoneCafiero](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@SimoneCafiero](https://discuss.elastic.co/u/SimoneCafiero)\
**Post date:** [October 10, 2017, 5:05pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/5 "2017-10-10T17:05:41Z")

</div>

Hi guys,  
ok it looks like you're discouraging the practice of appending a meaningful name to snap-_.dat and meta-_.dat files.

Anyway in different scenarios I saw that files renamed when using previous versions of ES in both FS and s3 repos based approach. Maybe it was considered as a way to allow a quick distinction when browsing them:

Having these:  
repo-name  
snaphot-name-prd-xyz

And then:  
snap-prd-xyz  
meta-prd-xyz

Anyway, thanks for clarifying.

Best,  
Simone

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 7, 2017, 5:05pm UTC](https://discuss.elastic.co/t/snapshot-endpoint-api-documentation/103404/6 "2017-11-07T17:05:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.