WebHooks: The API Strikes Back

WebHooks: The API Strikes Back

These days many APIs are more than just simple REST services. Nowadays, APIs want to talk back prompting further action from applications. But what is the best way to build out an API that can be demanding? We'll look at some services that use Webhooks, exploring reasons to use WebHooks and the emerging best practices. Then we'll look at the other side, implementing WebHook endpoints. Does consuming WebHooks turn an application into an API? What are the easiest ways to develop and test with WebHooks? We'll cover security, performance and standards all wrapped up with some live coded examples.

8ec1383b240b5ba15ffb9743fceb3c0e?s=128

Phil Nash

March 01, 2017
Tweet

Transcript

  1. 8.
  2. 15.

    Webhooks everywhere • Twilio • GitHub • Heroku • Braintree

    • Stripe • MailChimp • SendGrid • DropBox • ...and many more
  3. 16.
  4. 23.
  5. 24.
  6. 26.

    Sending Webhooks • Be a good HTTP client • Deal

    with failures • Sign requests
  7. 28.
  8. 29.
  9. 30.
  10. 31.
  11. 41.

    Webhooks • Tunnelling for development • Verify signatures • Use

    HTTPS • Respond quickly to Webhooks • Idempotence