ASC 2019 - API Specifications Conference

You have an awesome service, and you've crafted a beautiful REST API. You've got great API docs. What more could users possibly want?

This seems to be a common view of service teams, in my company and maybe also in yours.
I say: No one wants to call your API.

By that I mean, users may want the _result_ of your API, but they _do not_ want to deal with the details.

- How to craft the URL if it contains path parameters? That can be tricky!
- What credentials to use and how to pass them?
- Which headers to pass in the request? What headers to inspect in the response?
- How to construct a JSON request body from language objects?
- How to get language objects from a JSON response body?

In this talk, I'll discuss how to help your users avoid these and many other roadblocks to using your API by providing awesome client libraries, or SDKs, for your service.