Join Keith Casey for an in-depth discussion in this video What you should know before watching this course, part of Designing RESTful APIs.
- [Instructor] This course starts from the basis that you need to understand two primary things. First, you have to understand the business process that we're going to model. You can't build something you can't design, and you can't design something you can't describe. For this course, our business process is buying a book online. So it should apply to anyone watching this. Second, you need to understand that HTTP is expressive and can tell our users, and by extension, our applications using our APIs. A great deal of information and status that those applications can use.
HTTP is not perfect and it has some major weaknesses, but we can accomplish quite a bit with it anyway. And finally before we begin, I suggest you install a tool to view the HTTP headers. As in Firefox or Chrome, the live headers extension is sufficient, but the freely available Postman App is even better. On the command line I would suggest cURL. That's what most of my examples are throughout this course. Now we won't be writing any code in this course, but it's incredibly useful to open the extension and watch what data is actually provided in the headers while poking around with the APIs you probably already use.
That'll be even more important as you build your own API later.
- 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