Live data from Hacker News

Ask HN: What are good reads for designing APIs?

news.ycombinator.com

31–40 of 101 posts

Re: Ask HN: What are good reads for designing APIs?

#31

You'll notice in this thread that (at 9 comments in) there are no repeated recommendations. If the question was "What are some good reads for learning about algorithms?" you'd probably see the same handful of books being praised by everyone. Don't be overwhelmed by this though -- API design isn't an exact science. It's also very opinionated. Personally, I would just start reading actual API documentation (GitHub is a…

lets look at how not to design an http API

Re: Ask HN: What are good reads for designing APIs?

#34
I think it depends on what type of API you'd like to design.

If you're talking about REST APIs, then the best book I've come across is RESTful Web APIs by Leonard Richardson and Mike Amundsen:

http://restfulwebapis.org/

It actually shows you how to do REST properly, not that shoddy knock-off REST that some people push, where you have to document all your URI structures and hard-code them in your clients. There's solid examples that you build upon throughout each chapter, and jumping off points to standardisation work like JSON-LD etc.

Re: Ask HN: What are good reads for designing APIs?

#36

I'd recommend the original REST thesis from Roy Fielding. It's a bit lower level than most of the other things mentioned here, but helps get a good feeling for what is important to achieve in a RESTful web service.

Definitely, it is a great read.

Re: Ask HN: What are good reads for designing APIs?

#39

You'll notice in this thread that (at 9 comments in) there are no repeated recommendations. If the question was "What are some good reads for learning about algorithms?" you'd probably see the same handful of books being praised by everyone. Don't be overwhelmed by this though -- API design isn't an exact science. It's also very opinionated. Personally, I would just start reading actual API documentation (GitHub is a…

On that point, after you've read whichever of the many great recommendations you end up reading, don't get discouraged if you end up having to scrap the first several APIs you build. Part of the reason building APIs is so opinionated is that it's so difficult to do it well. Look at the API documentation for a bunch of different Google projects. Some of them are absolutely abominable. Others are quite good. Algolia has great documentation. When you get it wrong, you'll know. And that's all you really need to make sure you do better next time.

Re: Ask HN: What are good reads for designing APIs?

#40
API could be in any form - be it a dll lib, wcf or rest so I am pasting a resource for each.

1. Restful API with WCF - https://msdn.microsoft.com/en-us/library/dd203052.aspx

2. Restful API using WebAPI - https://github.com/Microsoft/api-guidelines/blob/master/Guid...

3. API via dll - https://www.amazon.com/Framework-Design-Guidelines-Conventio...

Post reply on HN