Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Understanding Async JS
Lesson Plan
  1. Introduction
    1. What is Asynchronous JS?
    2. Callbacks are not automatically asynchronous
    3. What is an API?
    4. Evolution of HTTP APIs
    5. Ajax vs Asynchronous JavaScript
  2. Fundamental Concepts
    1. How to fetch resources
    2. Using XHR
    3. Using the Fetch API
    4. Using libraries
    5. Core JavaScript concepts
    6. Understanding Promises
    7. Understanding Async Functions
    8. Understanding the Event Loop
    9. Understanding JSON
    10. Async JS Best Practices
    11. Using Optimistic UI
  3. Understanding Rest API
    1. Diving into Rest APIs
    2. The Rest Architecture
    3. The Rest Structure
    4. Anatomy of a Request
    5. What's an endpoint
    6. Request methods
    7. Understanding request headers
    8. Understanding the request body
    9. Authentication
    10. Basic Authentication
    11. Bearer Authentication
    12. Authenticating with API keys and API Secrets
    13. Cross Origin Resource Sharing
    14. Anatomy of a response
    15. HTTP Statuses
    16. Response headers
    17. The response body
    18. Handling Errors
    19. Reading API documentations
    20. Understanding Curl
  4. Node Basics
    1. Why we are using Node
    2. Command Line Basics
    3. Installing Node
    4. Managing dependencies
    5. Using ES Modules in Node
    6. Using Node
    7. Restarting the server automatically
    8. Sending requests via Node
    9. Protecting API keys and secrets
  5. Building a server
    1. What's a server
    2. Building a simple server with Express
    3. Two kinds of servers
    4. API Server architecture
    5. Handling routes
    6. Understanding Middlewares
    7. Enabling CORS
    8. Receiving data
    9. Sending responses
    10. Handling errors in Express
    11. Using the server as a proxy
    12. Minimum viable server
  6. Open Authorization
    1. Open Authorisation (OAuth)
    2. Authenticating with Access Tokens
    3. Obtaining Access Tokens
    4. Public and Confidential Clients
    5. Authorisation Code Grant
    6. Understanding scope
    7. Proof Key for Code Exchange (PKCE)
    8. PKCE with Twitter
    9. Dynamic state and `code_verifier`
    10. Saving the access token in cookies
    11. Passing access tokens to the browser
    12. Saving the access token in local storage
    13. Refresh Token Grant
    14. Device Code Grant
    15. Client libraries vs REST
  7. Building Social Media Logins
    1. Introduction
    2. Starter Files
    3. Creating SSL certificates
    4. Login in with Github
    5. Github: Saving the token to local storage
    6. Github: Persisting the login status
    7. Login with Twitter
    8. Twitter: Saving the token to local storage
    9. Twitter: Persisting the login status
    10. Twitter: Refreshing the access token
    11. Login with Facebook
    12. Facebook: Saving the token to localStorage
    13. Facebook: Persisting the login status
    14. Facebook: Refreshing the access token
    15. Login with google
    16. Google: Saving the token to localStorage
    17. Google: Refreshing the access token

What is an API?

2m:18s

You often hear the term API getting tossed around on the web. This acronym often comes with a technology prefix like Web API, REST API, and GraphQL API.

What do these mean?

To understand what these mean, you have to understand what an API is.

API stands for Application Programming Interface

Imagine there are two people in a room and they are trying to communicate.

Unfortunately, one person only speaks English while the other only speaks Chinese. It’s impossible for them to communicate because they don’t understand each other’s language.

Now, a translator comes into this room. This translator converts English to Chinese and Chinese to English. In doing so, the translator helps these two people communicate.

The same analogy applies to APIs.

We have three parties:

  • Your code
  • Code written by another person
  • And a set of rules in between that lets your code talk to the other set of code (and vice-versa).

This set of rules is the translator.

It’s the API.

Standardized APIs

Many APIs have been standardised so it becomes easy for us to use code that others have created.

These APIs are commonly given a name. Examples include:

  • Web API
  • Rest API
  • GraphQL

Each set of API contains different methods of communicating with code.

For example, you have methods that are only available in the DOM in the Web API, such as:

  • querySelector
  • classList
  • addEventListener

The reason why we can use these methods in every browser is because browser manufacturers follow the Web API.

If they didn’t, we would have to write lots of code to target each browser… which means we have to write a lot of browser-specific code.

// Example code if Web API is not standardized.
// This is pseudo-code that illustrates my point. (It doesn’t work).
const element =
safari.findElement() || firefox.selectElement() || chrome.getElement()

So the standardization of APIs is a great thing because it gives us a way to write code that others can use — and for others to write code in a way that we can use.

If you are curious, you can find a list of all available Web APIs methods inside MDN.

Rest, GraphQL, etc.

The prefix (Web, Rest, GraphQL, etc) gives you a way to identify what the API is about.

We already spoke about Web APIs so I won’t cover that again. If you are new to Web APIs, I suggest going through Learn JavaScript to have a thorough understanding of JavaScript and Web APIs.

Rest API and GraphQL are two different standards that have evolved around asynchronous JavaScript.

In the next lesson, we will look at the evolution of API standards to help you understand more about these terms.