Designing RESTful APIs

Designing RESTful APIs

English | MP4 | AVC 1280×720 | AAC 48KHz 2ch | 1h 24m | 207 MB

Having a solid understanding of how to correctly build APIs is important for any developer planning on creating websites. In this course, learn how to plan and model your own APIs, and explore the six REST design constraints that help guide your architecture. Keith Casey starts with a simple overview, including advice on identifying the users or “participants” of your system, and the activities they might perform with it. He discusses how to validate your design before you build it, and explores the HTTP concepts and REST constraints needed to build your API. To wrap up, Keith goes over some of the most common API design patterns you may encounter.

Topics include:

  • Approaches to adding an API
  • Modeling tips
  • Identifying activities and breaking them into steps
  • Mapping activities to verbs and actions
  • Creating and grouping API methods
  • Validating your API
  • HTTP headers and response codes
  • Common design challenges
  • Versioning best practices
  • Hypermedia and documentation approaches
Table of Contents

Introduction
1 Welcome
2 What you should know before watching this course

Who Needs Your API
3 Identifying activities and breaking them into steps
4 Identifying participants and activities to order a book online
5 Identifying participants
6 Three approaches to adding an API
7 Tips for modeling APIs
8 Why good API design is important

What Does Your API Look Like
9 Creating and grouping API methods
10 Mapping activities to verbs and actions
11 Validating your API

How Does Your API Work
12 HTTP headers and response codes
13 Overview of HTTP
14 REST APIs – The six constraints, part 1
15 REST APIs – The six constraints, part 2

Common Design Challenges
16 Advanced HTTP headers – Content negotiation and caching
17 Authentication and authorization
18 Choosing media types and processing content
19 Documentation approaches
20 Hypermedia approaches
21 SDK design considerations
22 Versioning best practices

Conclusion
23 Next steps