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

## The `info` section

The `info` section of the OAS file holds general information about the OpenAPI Specification, such as the `version` number of the specification (not the version of the implemented API, just the specification document), the `title`, and the `description`. It turns out that we supplied these values when the SwaggerHub Editor asked us to enter data in order to start the editing process. We can also add a comment block that contains some additional metadata about the specification, as shown in the following code:


# The `info` section

The `info` section of the OAS file holds general information about the OpenAPI Specification, such as the `version` number of the specification (not the version of the implemented API, just the specification document), the `title`, and the `description`. It turns out that we supplied these values when the SwaggerHub Editor asked us to enter data in order to start the editing process. We can also add a comment block that contains some additional metadata about the specification, as shown in the following code:


Learn how to create an OpenAPI document with SwaggerHub.

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

Creating Our OpenAPI Document with SwaggerHub

The `info` section

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

Creating Our OpenAPI Document with SwaggerHub

The info section

The `info` section