# REST API: Backwards compatibility? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 18, 2013, 8:15pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020 "2013-05-18T20:15:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Roy\_Russo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roy_russo/32/44835_2.png) [@Roy\_Russo](https://discuss.elastic.co/u/Roy_Russo)\ **Post date:** [May 18, 2013, 8:15pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/1 "2013-05-18T20:15:03Z")
I'm not sure if the devs monitor this list, but I'm seeing backwards incompatible changes occurring in the REST API, mainly between .90-\>1,0Beta1(git master). I'm curious if this is happening by design, or are they bugs? If by design, are there any plans to support versioning of the REST APIs? Regards, Roy Russo [http://www.elastichq.org](http://www.elastichq.org) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [May 18, 2013, 8:25pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/2 "2013-05-18T20:25:53Z")
Hi Roy Perhaps you could be more specific? clint On 18 May 2013 22:15, Roy Russo [royrusso@gmail.com](mailto:royrusso@gmail.com) wrote: > I'm not sure if the devs monitor this list, but I'm seeing backwards > incompatible changes occurring in the REST API, mainly between > .90-\>1,0Beta1(git master). > > I'm curious if this is happening by design, or are they bugs? If by > design, are there any plans to support versioning of the REST APIs? > > Regards, > Roy Russo > [http://www.elastichq.org](http://www.elastichq.org) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Roy\_Russo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roy_russo/32/44835_2.png) [@Roy\_Russo](https://discuss.elastic.co/u/Roy_Russo)\ **Post date:** [May 18, 2013, 9:26pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/3 "2013-05-18T21:26:39Z")
Hi Clinton, Sorry. I was working with a clean master build. Once I created the indexes, all was fixed and it looks like the APIs haven't changed. 😉 I'm assuming APIs and API responses don't change between versions. If they do, I'll have to do some fancy dynamic js loading on my side. On Saturday, May 18, 2013 4:15:03 PM UTC-4, Roy Russo wrote: > I'm not sure if the devs monitor this list, but I'm seeing backwards > incompatible changes occurring in the REST API, mainly between > .90-\>1,0Beta1(git master). > > I'm curious if this is happening by design, or are they bugs? If by > design, are there any plans to support versioning of the REST APIs? > > Regards, > Roy Russo > [http://www.elastichq.org](http://www.elastichq.org) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 18, 2013, 9:28pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/4 "2013-05-18T21:28:09Z")
They sometimes do - I noticed the MLT stuff recently changed On Sun, May 19, 2013 at 12:26 AM, Roy Russo [royrusso@gmail.com](mailto:royrusso@gmail.com) wrote: > Hi Clinton, > > Sorry. I was working with a clean master build. Once I created the > indexes, all was fixed and it looks like the APIs haven't changed. 😉 > > I'm assuming APIs and API responses don't change between versions. If they > do, I'll have to do some fancy dynamic js loading on my side. > > On Saturday, May 18, 2013 4:15:03 PM UTC-4, Roy Russo wrote: > > > I'm not sure if the devs monitor this list, but I'm seeing backwards > > incompatible changes occurring in the REST API, mainly between > > .90-\>1,0Beta1(git master). > > > > I'm curious if this is happening by design, or are they bugs? If by > > design, are there any plans to support versioning of the REST APIs? > > > > Regards, > > Roy Russo > > [http://www.elastichq.org](http://www.elastichq.org) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Roy\_Russo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roy_russo/32/44835_2.png) [@Roy\_Russo](https://discuss.elastic.co/u/Roy_Russo)\ **Post date:** [May 18, 2013, 9:33pm UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/5 "2013-05-18T21:33:20Z")
Right - which led me to the second part of my question asking if there was a standard with the ES dev team on versioning the REST API for backward compatibility support? On Saturday, May 18, 2013 4:15:03 PM UTC-4, Roy Russo wrote: > I'm not sure if the devs monitor this list, but I'm seeing backwards > incompatible changes occurring in the REST API, mainly between > .90-\>1,0Beta1(git master). > > I'm curious if this is happening by design, or are they bugs? If by > design, are there any plans to support versioning of the REST APIs? > > Regards, > Roy Russo > [http://www.elastichq.org](http://www.elastichq.org) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:35am UTC](https://discuss.elastic.co/t/rest-api-backwards-compatibility/12020/6 "2017-07-06T02:35:50Z")