StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>It sounds like you need to give the webhook receiver the option to choose whether or not to re-POST data when they register their endpoint with your service. I also highly recommend providing clear documentation how your service handles different response codes.</p> <p>It might be worth notifying the endpoint admin via email of the sync issues. This is more of a nice to have, as they can also always ping their own service or POST test data regularly.</p> <p>Also, consider this: What happens when <em>your</em> service fails. If sync is important, how does your service and the endpoint resolve that problem?</p> <p>You didn't provide too much context for what kind of data you're POSTing and what precise sync issues you're afraid of. Can you share more?</p> <p><strong>Edited</strong>: Here's <a href="http://apidocs.mailchimp.com/webhooks/" rel="nofollow">how MailChimp handles this issue</a>. They're clearly in the same boat as you are.</p> <blockquote> <blockquote> <blockquote> <p>When an event occurs that you have turned on, we'll send a HTTP POST request to the URL you've specified. If that URL is not available or takes too long to respond (more than 15 seconds), we'll cancel the request and try again later. Retries are done at increasing intervals over the course of 1 hour and 15 minutes. Those time frames may be tweaked as we start to receive feedback from users.</p> <p>For each event we'll return various data based on the event. Below is a sample data for each event - you can also easily see this using the PostBin tool mentioned above. Generally speaking, you'll see each event has a type and a fired_at field to help you track the type of event and get a timestamp (in GMT!) for the event.</p> </blockquote> </blockquote> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload