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

Receiving data

1m:55s

When you’re building an API server, you need to pay attention to three kinds of data:

  1. Data in the path
  2. Data in the query string
  3. Data in the body

Data in the path

Data in the path is often called a param.

In Express, you can write create paths with params with :, like this:

app.get('/path/:param', handler)

You can then get the param in the handler through req.params.

app.get('/path/:param', (req, res) => {
const { param } = req.params
})

You’ve already seen a real params example when you used Github’s API to get a user’s repositories in our previous examples.

fetch('https://api.github.com/users/zellwk/repos')

If we were to write this route handler in Express, it would look like this:

app.get('/users/:username/repos', (req, res) => {
const { username } = req.params
// Fetch repos associated with the username
})

Data in the query string

Data in the query string is also called query parameters.

You’ve seen this data when you change Github’s per_page query parameter to 100 in previous examples.

fetch('https://api.github.com/users/zellwk/repos?per_page=100')

We can get query parameters in Express through the query object.

app.get('/users/:username/repos', (req, res) => {
const { per_page } = req.query
// Do something with per_page
})

Data in the body

To get data in the body, you need to use Express’s built-in middlewares.

Here, you will need two middlewares:

// Middlewares
app.use(express.urlencoded({ extended: true }))
app.use(express.json())

Here’s what they’re used for.

  • express.urlencoded lets the server receive x-www-form-urlencoded data.
  • express.json lets the server receive json data

The extended option in express.urlencoded allows you to receive nested form data. This isn’t necessary but most developers have extended enabled because it’s a simple one-liner enhancement.

Now you can try sending in some form data and Express will be able to receive them.

<!-- In the client -->
<form method="post" action="/form">
<input type="text" name="message" />
<button type="submit">Send message</button>
</form>
app.post('/form', (req, res) => {
console.log(req.body)
})

You can also send in JSON data and Express will be able to receive them as well.

// In the client
zlFetch.post('https://localhost:3000/json', {
body: { message: 'hello' },
})
app.post('/json', (req, res) => {
console.log(req.body)
})