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

## Exercise
In this exercise, you’ll get a chance to work on modeling your own modified version of the Onboarding API. This timeyou’ll include the work of BigCo’s credit manager in the overall workflow. You’ll also be able to look at the form the credit manager uses for their work and convert that into your own internal cycles document to be used later (when we want to update the Onboarding API).

Follow the steps provided below to complete this challenge:

1. To start, move to the `credit-check` folder and take a look at the credit manager’s form as well as the credit-check story documents located in this folder.

2. Update the provided and partially filled-in `credit-check-workflow.txt` document to create your own workflow (`credit-check-workflow.txt`) that identifies all the actions needed to support the `credit-check-story.md` file.


> **Note:** You can use the `cat credit-check-story.md` command to view the story document and the `nano credit-check-workflow.txt` command to edit the workflow document. Press “Ctrl + S” and “Ctrl + X” after editing the document to save and exit.


# Exercise
In this exercise, you’ll get a chance to work on modeling your own modified version of the Onboarding API. This timeyou’ll include the work of BigCo’s credit manager in the overall workflow. You’ll also be able to look at the form the credit manager uses for their work and convert that into your own internal cycles document to be used later (when we want to update the Onboarding API).

Follow the steps provided below to complete this challenge:

1. To start, move to the `credit-check` folder and take a look at the credit manager’s form as well as the credit-check story documents located in this folder.

2. Update the provided and partially filled-in `credit-check-workflow.txt` document to create your own workflow (`credit-check-workflow.txt`) that identifies all the actions needed to support the `credit-check-story.md` file.


> **Note:** You can use the `cat credit-check-story.md` command to view the story document and the `nano credit-check-workflow.txt` command to edit the workflow document. Press “Ctrl + S” and “Ctrl + X” after editing the document to save and exit.


Try to model APIs on Credit-Check service.

Introduction

Understanding HTTP, REST, and APIs

Modeling APIs

Designing APIs

Describing APIs

Sketching APIs

Prototyping APIs

Building APIs

Build a Rest API for an Image-Sharing App With Node.js

Testing APIs

Securing APIs

Deploying APIs

Deploying a Web Application to Heroku Using CLI

Modifying APIs

Some Parting Thoughts

Appendixes

Challenge: Modeling APIs

Exercise