A collection of design practices that we have developed in collaboration with some of the leading API teams around the world, as they craft their API strategy through a design workshop that we provide at Apigee. We call our point of view in API design “pragmatic REST”, because it places the success of the developer over and above any other design principle. The devel
A quick overview of how to approach designing an API, with some examples to illustrate its points. This is good for anyone who's new to the subject, but would recommend following up with a more in-depth book.
A good short starting point for REST. If you are already familiar with REST best practices, it does not bring much new stuff. Available for free. If you want to dig a little bit deeper, look at Microsoft REST API Guidelines
A small book, with create example of how to design your API using best practice and common sense from a lot of good API's ( Foursquare, Twitter, Facebook ) He show how to do the stuff, how twitter/foursquare/facebook does - that could be the same or different and approach - and the pro and cons of any choice
Really useful resource for getting you started with designing of web apis. it covers several important topics like versioning, error handling, naming attributes, formats, header vs url parameters and so on. I addition, it covers strategies on how to deal with chatty apis, provide SDKs and, finally, patterns and anti-patterns.
The book could be seen as a compilation of several resources, with details in lots of topics and great tips about how to handle several issues while developing APIs. Like how to address the separation of resources, or which ways should you approach the architecture of the API.
It’s not completely focused on security (although there is some information about it, like Authentication), but more on maintainability and ease of use, from a developer point of view. Which is exactly what the title of the book suggests.
Definitely recommended if you're sort of a newby in the API design world. I've been researching for a month on this topic, and trying some simple solutions too. This book is helpful and leads you on the proper way to build a sustainable, accessible and clear API.
Hardly a book (38 pages only), but nice collection of REST best-practices and well-designed API recommendations. Valuable is comparison of main players, leaders in given domain like Twitter, Facebook, Google at al.
But be careful - this is intended for API designers, so study & practice REST basics first, before approaching of this booklet.
A conclusion is a little bit weak - Facade from GoF. I would expect something more beneficial.
This very very very pragmatic "book" give a good overview about the design aspects of APIs. Some of the guides can be used for non-web APIs, too. I like the idea of these book style. It has around 50 pages. So it`s good for a short travel or an evening lecture. You cant expect code in this book, so it is more or less a collection of DOs and DONTs in API-Design. But I can recommend it and it is worth to read.
It was fine, I guess. Not nearly enough detail for me, though--I knew I should paginate responses before reading this, what I really wanted to know was what would be the best way of going about doing so. Send a full URL? Just a "next page" number? Dealing with complex associations was another area that could have been covered in more detail.
A good introductory manual on good practices in API design, specifically on REST API design. It's very basic but it's definitely a good book to get started.
Пользоваться некоторыми советами из этой книги для проектирования интерфейса больших серьёзных систем вредно. Остальные — не представляют особой ценности.