Gain insights into designing robust APIs, explore essential tools for design, documentation, testing, and deployment. Delve into ALPS, OpenAPI, Postman, and Heroku for comprehensive API development.

Design and Build Great Web API's by The Pragmatic Programmer-01.png

webapis.tar.gz

Testing APIs

Testing API Exercise

Building API Exercise

Building API Exercise Solution

Securing API Exercise

Securing API Exercise Solution

MockAPI

Account Mock API

Company service Mock API

Challenge-1 Mock API Solution

Postman Mock API

At the start of this course, you’ll be introduced to a handful of important practices and principles for designing and building APIs that are robust, reliable, and resilient. You’ll also acquire skills in a wide range of developer tools, including tools for design, documentation, building, testing, security, and deployment. 

You'll learn the best practices for modeling an APIs lifecycle using Donald Norman’s action lifecycle. Then, you’ll learn how to use the sequence diagram for designing APIs and describing them using ALPS. For sketching an API, you will learn about Gehry's sketches. You will also cover OpenAPI and SwaggerHub for API mocking. Moreover, the usage of DARRT and NodeJS will be covered for building APIs. You'll finish with learning how to use the Postman for testing APIs and then deploy them using Heroku.

By the end of this course, you will have an in-depth understanding of how to make fully functional efficient APIs from its inception to its deployment.

Design and Build Great Web APIs

# Resources in the DA**R**RT framework
Now, it’s time to implement all the externally addressable API endpoints, or **resources**, for this service. We do that in the `resources.js` file of the DARRT framework. The reference diagram for our external endpoints is the one we created earlier. To refresh our memory, it looks like this:


The key elements on this diagram (items in oval shapes) are the external endpoints of our HTTP API. This diagram also tells us which HTTP methods are supported for each resource. That’s what we need to implement in our `resources.js` file—not just the endpoints, but also the methods to be supported.

The following is a quick rendering of the `resources.js` file with all the endpoints and methods added in. There’s no code in any of these yet, we’ll be adding it shortly. For now, scan the list of operations and note how they match up with the diagram:


Learn about the resources in a DARRT project.

Introduction

Understanding HTTP, REST, and APIs

Modeling APIs

Designing APIs

Describing APIs

Sketching APIs

Prototyping APIs

Building APIs

Testing APIs

Securing APIs

Deploying APIs

Modifying APIs

Some Parting Thoughts

Appendixes

DARRT Project: Resources

Resources in the DARRT framework