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

## Representation in DAR**R**T framework
The second R in DARRT stands for **representation**. This refers to the format of the HTTP API responses. HTTP APIs can use a wide variety of formats to represent HTTP responses. The most common response for APIs today is plain JSON (`application/json`), but a number of other formats also exist.

In the DARRT framework, we can vary the response representations by simply loading one of the preset formats and referencing them when implementing the API. For this course, we’ve collected a small set of formats. Each of them was implemented using the EJS (Embedded JavaScript templating) templating engine for Node.js. These templates are provided in the `darrt/representors/` folder. You check these templates by executing the `cd representors` and `ls` commands in the terminal below.


# Representation in DAR**R**T framework
The second R in DARRT stands for **representation**. This refers to the format of the HTTP API responses. HTTP APIs can use a wide variety of formats to represent HTTP responses. The most common response for APIs today is plain JSON (`application/json`), but a number of other formats also exist.

In the DARRT framework, we can vary the response representations by simply loading one of the preset formats and referencing them when implementing the API. For this course, we’ve collected a small set of formats. Each of them was implemented using the EJS (Embedded JavaScript templating) templating engine for Node.js. These templates are provided in the `darrt/representors/` folder. You check these templates by executing the `cd representors` and `ls` commands in the terminal below.


Learn about the role of representation in the DARRT framework.

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

DARRT Project: Representation

Representation in DARRT framework