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.

Find out more

Build APIs You Won't Hate

Everyone and their dog wants an API, so you should probably learn how to build them.

Tasked with building an API for your company but don't have a clue where to start? Taken over an existing API and hate it? Built your own API and still hate it? This book is for you.

This book has been up on the LeanPub top 10 for most of its lifetime, and was #5 Best Selling Book of 2015, so it can't be too bad.

Find out more

About This Community

API development is a topic very close to Phils heart. APIs You Won't Hate started out as a book, with Phil pouring everything API related he knew, all the problems he faced, all the design decisions he wish he thought about earlier.

Since the book, Phil has continued to learn and grow, thanks to new experiences, and new conversations with really smart people. Learning never stops, and the Slack channel that grew from the book subscribers and their friends has become home to the largest API chat group on the internet.

APIs You Won't Hate is dedicated to learning, writing, sharing ideas and bettering understanding of API practices. Together we can erradicate APIs we hate.

Get pragmatic API, HTTP and REST info monthly!
Not into mailing lists? Get all modern with Slack. We're the largest API-centric Slack channel around. Get your API, REST and HTTP questions answered by 2,000+ people.

About Phil Sturgeon

Since 2010 I've worked as a freelancer, consultant, Head of API, and CTO, for several API-centric technology startups.

Previously at Ride, I was given me the chance to work with amazing developers, including several Rails API contributors. We built an event-driven architecture with several REST APIs and a few RPC ones, and it was here I learned the benefits of REST being a state machine over HTTP.

Now at WeWork, I am using my experience to help educate developers, define standards for API design and architecture, and work on open-source tooling for OpenAPI, JSON Schema, and HTTP. WeWork has 50+ APIs, and here I have had a chance to learn a lot about keeping distributed applications performant. Tmeouts, retries, circuit breakers, keep alive settings, and HTTP caching specificially.

I try to turn all of this learning into books, videos, and articles, so others can learn easily things I've had to learn the hard way.