Surviving Other People's APIs

Designing the worlds most beautiful API is only half the story, somebody needs to interact with it!

API Developers focus so much on designing and building their APIs, yet often we seem to forget the folks on the other end of the line. You, the frontend and backend developers trying to integrate our data and functionality into your own work, often get left with junky docs, or are just assumed to know how things are going to work.

About the book

Frontend engineers work magic. They deal with all sorts of awful browser stuff, and have to deal with all sorts of ginormously complex problems. Most of those problems seem to be browser compatibility and Webpack, but there's a lot of documentation around how most of these things work. One area where frontend engineers are often left entirely in the dark? Interacting with APIs.

Following the success of Build APIs You Won’t Hate, this book will take a non-academic, easy-to-read approach to some pretty complex topics around HTTP interactions, versioning, client-caching, state management, differences between how you interact with RPC, REST and GraphQL, using JSON Schema for local validation, and all sorts of other awesome stuff that nobody ever bothered to mention.

This book is aimed at frontend engineers (web, mobile, whatever) and backend engineers that find themselves talking to other APIs a lot, which is probably most of us these days.

About Phil Sturgeon

Over the last five years I've worked as a freelancer, consultant, Head of API, and CTO, for several API-centric technology startups. The most recent, Ride, has given me the chance to work with several amazing developers, including several Rails API contributors. Ride let me share our API experiences at conferences world-wide, which is an amazing opportunity to educate others on a topic I'm incredibly passionate about.

Spending that much time building APIs means I have a long list of ways to make them not suck, and I would like to that with you lot. The book covers everything learned from years of doing this day in day out, and it tries to keep it light and breezy: through what could otherwise be some rather dull topics.

For more about APIs, you can check out my blog, and specifically the #api tag.