# OpenSource API Doc

**URL:** <https://forum.beeminder.com/t/opensource-api-doc/2012>\
**Category:** Tech\
**Created:** [March 10, 2016, 10:26pm UTC](https://forum.beeminder.com/t/opensource-api-doc/2012 "2016-03-10T22:26:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave42w](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dave42w/32/1020_2.png) [@dave42w](https://forum.beeminder.com/u/dave42w)\
**Post date:** [March 10, 2016, 10:26pm UTC](https://forum.beeminder.com/t/opensource-api-doc/2012/1 "2016-03-10T22:26:48Z")

</div>

Just wondering if you might consider opening the source for the API docs. Or at least providing a way to submit patches as suggestions. Might make it less work for you to get clarifications in.

Thanks

---

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [March 11, 2016, 7:20am UTC](https://forum.beeminder.com/t/opensource-api-doc/2012/2 "2016-03-11T07:20:27Z")

</div>

That sounds amazing. We actually currently have the source for the documentation on an etherpad, which gets pulled in to the git repo for deploys. So not the best setup for public sharing. But since you’ve proven yourself conscientious and super sharp I’ll just give you direct access. Emailing you now…

(Everyone else, please click the little heart to vote for us open-sourcing the docs (among other things) and email me – [dreeves@beeminder.com](mailto:dreeves@beeminder.com) – if you’ve made your awesomeness known in the forums such that I might be fine with giving you direct edit access as well.)

See also:

> [@API version 2 planning and wishlist](http://forum.beeminder.com/t/api-version-2-planning-and-wishlist/509):
>
> This is a wiki for starting to sketch version 2 of the Beeminder API. Huge thanks to @insti for help in thinking this through so far. Here are some principles we may want to adopt: Wishlist All queries should return json. Requests should be able to be made using json. (This has the advantage of not requiring array data such as road matrices and datapoints to be json encoded and then url encoded as in v1) e.g.: curl -X POST -H "application/json" -d '{"slug": "mygoal", "road":[["20150213"…

---

<div class="post-metadata">

**Author:** ![dave42w](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dave42w/32/1020_2.png) [@dave42w](https://forum.beeminder.com/u/dave42w)\
**Post date:** [March 13, 2016, 8:50am UTC](https://forum.beeminder.com/t/opensource-api-doc/2012/3 "2016-03-13T08:50:38Z")

</div>

I made my first tiny contribution to the docs last night.

I used the browser based EtherPad as I looked at the installation instructions for Ubuntu and thought, no way 🙂