In today’s market, where rival web services compete for attention, a well-designed REST API is a must-have feature. This concise book presents a set of API design rules, drawn primarily from best practices that stick close to the Web’s REST architectural style. Along with rules for URI design and HTTP use, you’ll learn guidelines for media types and representational forms. Using these simple rules, you will design web service APIs that adhere to recognized web standards.
On Aug 31 Rob Dawson wrote: REST + WRML
The book provides a decent set of information around REST, and had me either nodding my head or thinking at various stages. Its description and thoughts around REST were pretty good, but there is one area to be wary of. The book seems to do two things.
Describe ways of doing REST well.
Sell WRML, the authors own framework to help model REST Full Review >
On Jul 17 Hari K T wrote: REST API Design Rulebook by Mark Massé; O'Reilly Media
Everyone has been hearing the buzz REST. As web services and api for websites are becoming popular, all are busy developing REST api's for their websites.
What exactly is REST?
REpresentational State Transfer (REST) is a style of software architecture for distributed systems such as the World Wide Web. REST has emerged over the past few years as a predominant Web service design model. This is what wiki mentions .
The book REST API Design Rulebook by Mark Massé; O'Reilly Media will teach you some rules which needs to be followed. This book has really helped me to understand some of the basic concepts of HTTP protocol. Yes really I was able to understand more on REST and how it should be represented etc.
Probably you would have noticed websites with format .... Full Review >
On Jun 17 Tushar Jain wrote:
Full Review >
On Jun 12 Rob Friesel wrote: good introduction to REST APIs (could do w/o the WRML evangelizing)
If you're new to the world of REST APIs, and if you're looking for a good set of working rules on how to design them, then Mark Massé's "REST API Design Rulebook" should live up to its title just fine. It's a short book (you could read it in an afternoon) and it tackles the subject matter in a direct and orderly fashion. For me, the highlight reel included: the first three chapters (on identifier design, interaction design, and metadata design), and some of the discussion in the final chapter ("Client Concerns") about security, and the overview (however brief) of JSONP and CORS as solutions for some otherwise challenging situations. Full Review >
On May 30 Eder Andres Avila Nino wrote: An Attempt to Unify the REST APIs
This a good book for beginners willing to understand what a REST API is about, its characteristics, HTTP methods and media resources in a short, concise, panoramic way. This book is an attempt to collect the best practices to expose the external behavior that a client, web or mobile. Experts can take an implicit 'audit' checklist to verify that their APIs are REST compliant. Full Review >
On May 25 Philip Choi wrote:
Full Review >