<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Giuliano Iacobelli</title>
    <description/>
    <link>https://speakerdeck.com/giulianoiacobelli</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/giulianoiacobelli.rss"/>
    <lastBuildDate>2017-10-04 19:21:55 -0400</lastBuildDate>
    <item>
      <title>Webhooks do's and dont's</title>
      <description>As modern applications are becoming more and more a composite of APIs and the serverless architectures are getting more attention, API providers can’t afford any longer to expose only traditional REST endpoints.

When it comes to designing webhooks there is nothing really close to a standard in the HTTP API literacy. Every service implements webhook differently leading to many different flavors of webhooks implementations out there.

After integrating APIs from more than 100 different services I can tell that the way a service exposes webhooks can be a deal breaker. So here are the things that make us happy when we need to integrate with a service exposing webhooks.</description>
      <media:content url="https://files.speakerdeck.com/presentations/46eb1a0c439641b38f790c6a5520289b/preview_slide_0.jpg?8693479" type="image/jpeg" medium="image"/>
      <content:encoded>As modern applications are becoming more and more a composite of APIs and the serverless architectures are getting more attention, API providers can’t afford any longer to expose only traditional REST endpoints.

When it comes to designing webhooks there is nothing really close to a standard in the HTTP API literacy. Every service implements webhook differently leading to many different flavors of webhooks implementations out there.

After integrating APIs from more than 100 different services I can tell that the way a service exposes webhooks can be a deal breaker. So here are the things that make us happy when we need to integrate with a service exposing webhooks.</content:encoded>
      <pubDate>Wed, 27 Sep 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/giulianoiacobelli/webhooks-dos-and-donts</link>
      <guid>https://speakerdeck.com/giulianoiacobelli/webhooks-dos-and-donts</guid>
    </item>
  </channel>
</rss>
