# Webhook/Callback documentation?

**URL:** <https://forum.beeminder.com/t/webhook-callback-documentation/313>\
**Category:** Tech\
**Created:** [December 12, 2014, 8:26am UTC](https://forum.beeminder.com/t/webhook-callback-documentation/313 "2014-12-12T08:26:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [December 12, 2014, 10:38am UTC](https://forum.beeminder.com/t/webhook-callback-documentation/313/2 "2014-12-12T10:38:08Z")

</div>

They’re triggered whenever Beeminder gets a new datapoint and nothing happens when they fail. If you wanted it to be super robust I think you’d want to periodically sync it with the [datapoints endpoint of the API](https://www.beeminder.com/api#dataall). The format is JSON and should be pretty self-explanatory. I’d recommend just setting the callback to something that echoes what it receives and then add a test datapoint to see what gets sent.

As for code that parses callbacks, check out [Paul Fenwick’s Exobrain](https://github.com/pjf/exobrain "Exobrain is an open-source and self-hosted (indieweb) version of Zapier or IFTTT").

I’m guessing we don’t quibble about self-signed certs but I guess that too is easy to check. Let us know if you think we’re doing the wrong thing in that regard!

PS: Curious to hear what awesomeness you’re cooking up!

PPS: The original idea for this callback feature was to enable [PESOS](http://indiewebcamp.com/PESOS "Publish Elsewhere, Syndicate to Own Site") – keeping a realtime mirror on your own site of all your Beeminder data. It has turned out to mostly be useful for other, even awesomer, things.

---

_[View the full topic](https://forum.beeminder.com/t/webhook-callback-documentation/313)._
