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
A folder named `services` has been provided that contains a series of API calls (via HTTP). We’ve used `curl` to make requests to BigCo’s existing services and saved the responses to that folder.

> **Note:** You can see the `services` folder’s content by executing `cd services` and `ls` commands in the terminal provided below.

The task for this challenge is to move the `services` folder (and all the API calls stored there) into the project repository.

Follow the steps provided below to complete this challenge:

1. Create a directory named `onboarding` and initialize an empty Git repository using the `git init` command.
2. Copy the `ch02-http/git-readme.md` file to the `onboarding` folder using `cp` command.
3. Move to the `onboarding` folder and add the `git-readme.md` file to Git using the   `add` command.
4. Commit the changes using `git commit -m"Add Readme file"`.
5. Execute `git status` to check the status.
6. Move the `services` folder to the `onboarding` folder by executing the `mv ../services .` command in `onboarding`.
7. Now, use `git add` and `git commit` commands to commit those changes to the local repository.
8. Then use the `git push` command to push local changes to the shared GitHub repository in the cloud. To push local changes to the public GitHub repository, execute `git remote add origin git@github.com:mamund/onboarding.git`, `git branch -M main`, and `git push -u origin master`. Use your GitHub repository link instead of `mamund/onboarding.git`.


> **Note:** Don’t forget to use the `git config` command before committing any changes to the repository.


## Terminal

# Exercise
A folder named `services` has been provided that contains a series of API calls (via HTTP). We’ve used `curl` to make requests to BigCo’s existing services and saved the responses to that folder.

> **Note:** You can see the `services` folder’s content by executing `cd services` and `ls` commands in the terminal provided below.

The task for this challenge is to move the `services` folder (and all the API calls stored there) into the project repository.

Follow the steps provided below to complete this challenge:

1. Create a directory named `onboarding` and initialize an empty Git repository using the `git init` command.
2. Copy the `ch02-http/git-readme.md` file to the `onboarding` folder using `cp` command.
3. Move to the `onboarding` folder and add the `git-readme.md` file to Git using the   `add` command.
4. Commit the changes using `git commit -m"Add Readme file"`.
5. Execute `git status` to check the status.
6. Move the `services` folder to the `onboarding` folder by executing the `mv ../services .` command in `onboarding`.
7. Now, use `git add` and `git commit` commands to commit those changes to the local repository.
8. Then use the `git push` command to push local changes to the shared GitHub repository in the cloud. To push local changes to the public GitHub repository, execute `git remote add origin git@github.com:mamund/onboarding.git`, `git branch -M main`, and `git push -u origin master`. Use your GitHub repository link instead of `mamund/onboarding.git`.


> **Note:** Don’t forget to use the `git config` command before committing any changes to the repository.


# Terminal

Try to push local changes to the shared GitHub repository in the cloud.

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: Understanding HTTP, REST, and APIs

Exercise