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

# Transitions in the DARR**T** framework
The last letter in our DARRT framework stands for **transitions**. The `transitions.js` file holds a set of declarations for forms and links related to the API. An example of a link transition in HTML is the anchor (`<a>`)tag:

```html
<a href="/list/" rel="collection list company">Company List</a>
```

An example of a form transition in HTML is the `form` tag:

```html
<form action="/filter/" method="get">
   <input name="search" value="" />
   <input type="submit" />
</form>
```

HTML format has lots of **transition elements**—elements that describe a way to transition from one view to the next. Several API formats support link and form transitions too. We discussed the role HTML plays in the common practice of the web. Because one of our goals in creating APIs is to learn from and emulate features of the web, the DARRT framework was designed to allow developers to declare and use transitions in API responses.

Just as in HTML, adding transitions to API responses informs the API caller of the next possible actions in the API workflow. Like HTML, well-designed APIs don’t have just one possible fixed sequence of actions. Instead, users (people for HTML, machines for APIs) can make their own choices on what steps to take next.

The following is what a transition looks like in the `transitions.js` file of the DARRT framework (it’s similar to the HTML anchor tag we saw earlier):

Learn about the role of transitions in the DARRT framework.

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: Transitions

Transitions in the DARRT framework