RESTfulWebAPIs

RESTful APIs make programming easy for users, but it can be tricky to map traditional APIs to REST expectations. While REST simplifies user expectations, getting the flow and granularity of data right remains a challenge. REST's popularity has led to tremendous growth in 'almost REST' APIs, and growPraise for restful web aplsThis book is the best place to start learning the essential craft of API DesignMatt McLartyCofounder, API AcademyThe entire time i read this book, i was cursing i was cursing because as i read eachexplanation, I was worried that they were so good that it would be hard to find a better oneto use in my own writing. You will not find another work that explores the topic sothoroughly yet explains the topic so clearly. Please, take these tools, build somethingfantastic, and share it with the rest of the world, okay?-Steve klabnikAuthor, Designing Hypermedia APIsWonderfully thorough treatment of hypermedia formatsREST s least well understood tenetStefan TilkowREST evangelist, author, and consultantThe best practical guide to hypermedia APIs. A must-haveRuben terborghSemantic hypermedia researcherwww.finebook.irwww.finebook.irRESTful Web aplsLeonard richardson and mike amundsenForeword by sam rubORE|LLY°Beijing· Cambridge. Farnham:Kdln· Sebastopol· Tokyowww.finebook.irRESTful Web aplsby Leonard richardson and mike amundsen with a Foreword by Sam RubyCopyrightO2013LeonardRichardson,amundsen.com,Inc,andSamRuby.AllrightsreservedPrinted in the United States of AmericaPublished by O reilly Media, Inc, 1005 Gravenstein Highway North, Sebastopol, CA 95472OReilly books may be purchased for educational, business, or sales promotional use. Online editions arealsoavailableformosttitles(http://my.safaribooksonline.com).Formoreinformation,contactourcorporateinstitutionalsalesdepartment800-998-9938orcorporate@oreilly.comEditors: Simon St. Laurent and Meghan blanchette Indexer Judith McconvilleProduction Editor Christopher HearseCover Designer: Randy comerCopyeditor: Jasmine KwitynInterior Designer: David FutatoProofreader Linley dolbyllustrator: Rebecca demarestSeptember 2013: First EditionRevision History for the First Edition2013-09-10 First releaseSeehttp://oreilly.com/catalog/errata.csp?isbn=9781449358068forreleasedetailsNutshell Handbook, the Nutshell Handbooklogo, and the O Reilly logo are registered trademarks ofO ReillyMedia, Inc. RESTful Web APIs, the image of Hoffmanns two-toed sloth, and related trade dress are trademarks of o Reilly media, IncMany of the designations used by manufacturers and sellers to distinguish their products are claimed arademarks. Where those designations appear in this book, and OReilly Media, Inc, was aware of a trademark claim, the designations have been printed in caps or initial capsWhile every precaution has been taken in the preparation of this book, the publisher and authors assumeno responsibility forerrors or omissions, or for damages resulting from the use of the information containedhereinISBN:978-1-449-35806-8[LSIwww.finebook.irFor Sienna, Dalton, and Maggie -LeonardFor Milo The Supervisor, my constant and patient companion throughout this and somany other projects. Thanks, buddy ! -Mikewww.finebook.irwww.finebook.irTable of contentsForewordIntroduction1. Surfing the Web.Episode 1: The BillboardResources and representationsaddressabilityEpisode 2 The Home PageShort sessionsSelf-Descriptive MessagesEpisode 3 The Link22334568Standardized methodsEpisode 4: The Form and the redirectApplication State10Resource stateConnectedness13The Web Is Something Special14Web aPis lag behind the Web15The Semantic Challenge162. A Simple APl..............Http Get: Your Safe Bet18How to Read an Http Response18JSONCollection+ jSON21Writing to an API22Http Post: How Resources are born24Liberated by constraints25www.finebook.irApplication Semantics Create the Semantic Gap273. Resources and Representationsa Resource can be anythinsgA Representation Describes Resource StateRepresentations Are Transferred Back and Forth31Resources with Many Representations32TheProtocolSemanticsofhttp33GETDELETE35impotence36POST-to-Append37PUT37PATCH38LINK and UNLINK39HEADOPTIONSOverloaded POSt41Which Methods Should You use?424. Hypermedia.45HTML as a Hypermedia FormatURI Templates49URI Versus url50The Link header51What Hypermedia Is For52Guidinggthe request52Promises About the response53Workflow Control54Beware of Fake Hypermedia!The Semantic Challenge: How are We doing?565. Domain-Specific Designs59Maze+ XML: A Domain-Specific DesignHow Maze+XMl Works61Link relations62Follow a Link to Change application State64The Collection of mazes65Is Maze+XMl an api?67Client #1: The Game68A maze+XML server72Client #2: The MapmakerTable of contentswww.finebook.ir