By now you have a frontend, a server, and a database, but they still need a way to talk to each other. An API is that bridge: a set of agreed-upon endpoints the frontend can call to read and change data on the server. Building a good one, and consuming it cleanly, is where the two halves of full stack development meet.
You'll start with REST, the most common style for designing APIs around resources and standard HTTP methods, then look at GraphQL, an alternative that lets the client ask for exactly the data it needs. Because API calls take time to come back, you'll also cover promises and async/await, the tools JavaScript gives you for writing the frontend code that fetches and handles that data.
With the two halves connected, you'll be ready for the next module, Authentication & Security, where you'll control who can call your API and protect it against common attacks.
The core ideas behind REST APIs, including resources, URLs, and HTTP methods, shown through worked examples of requests and responses.
A quick introduction to GraphQL, a query language for APIs that lets the client request exactly the data it needs in a single call.
A short look at promises, the JavaScript feature for handling work that finishes later, such as waiting for a response from an API.
How async/await makes asynchronous code read like normal step-by-step code, and how to use it when fetching data from an API.