# When to use PUT versus POST?

**URL:** <https://discuss.elastic.co/t/when-to-use-put-versus-post/68550>\
**Category:** Elasticsearch\
**Created:** [December 9, 2016, 11:00am UTC](https://discuss.elastic.co/t/when-to-use-put-versus-post/68550 "2016-12-09T11:00:24Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [December 9, 2016, 3:30pm UTC](https://discuss.elastic.co/t/when-to-use-put-versus-post/68550/3 "2016-12-09T15:30:34Z")

</div>

> [@dadoonet](#):
>
> It's all about REST semantics.

And our understanding of the semantics at the time when we made the APIs. And backwards compatibility constraints. And whatever "feels" natural to the person who implemented the API.

Where it makes a lot of sense Elasticsearch maps the HTTP verbs to useful things. But when it doesn't make a ton of sense we just go with whatever verb feels good rather than trying to be super strict about REST. Also, we don't do linked data, instead relying on you to build links from context. I'm told that is particularly non-REST. But it is what we do.

---

_[View the full topic](https://discuss.elastic.co/t/when-to-use-put-versus-post/68550)._