Fetching APIs in frontmatter in Astro - Step-by-Step Execution

Concept Flow - Fetching APIs in frontmatter

Start Astro file

↓

Frontmatter block begins

↓

Fetch API data asynchronously

↓

Store fetched data in variables

↓

Frontmatter block ends

↓

Use data in template to render

↓

Page renders with API data

Astro fetches API data inside the frontmatter before rendering the page template.

Execution Sample

Astro

---
const response = await fetch('https://api.example.com/data');
const data = await response.json();
---
<h1>{data.title}</h1>

This code fetches JSON data from an API in the frontmatter and displays the title in the page.

Execution Table

Step	Action	Evaluation	Result
1	Start frontmatter	Begin async code	No output yet
2	Call fetch('https://api.example.com/data')	Wait for response	Response object received
3	Call response.json()	Parse JSON body	JavaScript object stored in 'data'
4	End frontmatter	Variables ready for template	data available for rendering
5	Render <h1>{data.title}</h1>	Insert data.title value	Page shows title text

💡 Frontmatter completes after data is fetched and parsed, then template renders with data.

Variable Tracker

Variable	Start	After fetch	After json()	Final
response	undefined	Response object	Response object	Response object
data	undefined	undefined	Parsed JSON object	Parsed JSON object

Key Moments - 3 Insights

Why do we use 'await' with fetch in frontmatter?

Because fetch returns a promise, 'await' pauses execution until the data arrives, as shown in execution_table step 2.

Can we use the fetched data directly in the template?

Yes, after frontmatter finishes, variables like 'data' are ready for the template, as seen in execution_table step 5.

What happens if we forget 'await' before fetch?

The variable 'response' would hold a promise, not the actual data, causing errors when calling response.json(), as implied in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'data' after step 3?

A Parsed JSON object

B Undefined

C A promise object

D Response object

💡 Hint

Check the 'Result' column at step 3 in execution_table.

At which step does the frontmatter finish and template rendering start?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look for 'End frontmatter' action in execution_table.

If we remove 'await' before fetch, what changes in variable_tracker for 'response' after fetch?

A It becomes a Response object

B It becomes undefined

C It becomes a Promise object

D It becomes the parsed JSON

💡 Hint

Recall that fetch returns a promise and 'await' unwraps it, see key_moments explanation.

Concept Snapshot

Astro frontmatter runs before rendering.
Use 'await fetch(url)' to get API data.
Parse JSON with 'await response.json()'.
Store data in variables for template use.
Template renders with fetched data synchronously.

Full Transcript

In Astro, you write code inside the frontmatter block at the top of your file. Here, you can fetch data from APIs using the fetch function with await to pause until the data arrives. After fetching, you parse the response as JSON and store it in a variable. Once the frontmatter finishes, the template below can use this data to render content. This process ensures your page shows fresh API data when it loads.

Practice

1. What is the main purpose of fetching APIs in the frontmatter of an Astro component?

easy

A. To get data before the page renders so it shows fresh content immediately

B. To delay data loading until after the page is fully loaded

C. To style the page using CSS variables

D. To handle user input events on the page

Solution

1. Step 1: Understand frontmatter role in Astro

   Frontmatter runs before the page renders, allowing data fetching early.

2. Step 2: Purpose of fetching API in frontmatter

   Fetching data here ensures the page shows fresh content immediately when loaded.

3. Final Answer:

   To get data before the page renders so it shows fresh content immediately -> Option A

4. Quick Check:

   Fetching in frontmatter = fresh data before render [OK]

Hint: Frontmatter fetches data before page shows [OK]

Common Mistakes:

• Thinking data loads after page renders
• Confusing frontmatter with styling or events
• Assuming frontmatter runs on client side

2. Which of the following is the correct syntax to fetch data in Astro frontmatter?

easy

A. ---
const response = await fetch('https://api.example.com/data');
const data = await response.json();
---

B.

C. const data = fetch('https://api.example.com/data');

D. ---
fetch('https://api.example.com/data')
---

Solution

1. Step 1: Identify frontmatter syntax

   Astro frontmatter uses triple dashes --- to enclose code that runs before rendering.

2. Step 2: Correct async fetch usage

   Using await fetch and await response.json() inside frontmatter is correct to get JSON data.

3. Final Answer:

   --- const response = await fetch('https://api.example.com/data'); const data = await response.json(); --- -> Option A

4. Quick Check:

   Frontmatter uses --- and await fetch [OK]

Hint: Use --- and await fetch inside frontmatter [OK]

Common Mistakes:

• Using fetch without await in frontmatter
• Placing fetch inside <script> tag instead of frontmatter
• Not parsing response with .json()

3. Given this Astro frontmatter code, what will be the value of data.message in the component?

---
const response = await fetch('https://api.example.com/greet');
const data = await response.json();
---

{data.message}

Assuming the API returns JSON: { "message": "Hello, Astro!" }

medium

A. undefined

B. "Hello, Astro!"

C. SyntaxError

D. null

Solution

1. Step 1: Understand fetch and JSON parsing

   The fetch gets the API response, and await response.json() parses it into an object with a message property.

2. Step 2: Accessing data.message in component

   The component uses {data.message} which will display the string from the API: "Hello, Astro!".

3. Final Answer:

   "Hello, Astro!" -> Option B

4. Quick Check:

   API message property = "Hello, Astro!" [OK]

Hint: Parsed JSON data shows in component as expected [OK]

Common Mistakes:

• Forgetting to await response.json()
• Trying to access data before fetch completes
• Assuming data.message is undefined or null

4. What is wrong with this Astro frontmatter code?

---
const data = fetch('https://api.example.com/data');
const json = data.json();
---

medium

A. Using triple dashes --- incorrectly

B. json() is not a function

C. fetch URL is invalid syntax

D. Missing await before fetch and json() calls

Solution

1. Step 1: Check async fetch usage

   fetch returns a Promise, so it must be awaited to get the response object.

2. Step 2: Check json() call

   response.json() also returns a Promise and must be awaited to get parsed data.

3. Final Answer:

   Missing await before fetch and json() calls -> Option D

4. Quick Check:

   Always await fetch and response.json() [OK]

Hint: Always await fetch and json() in frontmatter [OK]

Common Mistakes:

• Not using await causing unresolved Promises
• Assuming fetch is synchronous
• Calling json() on Promise instead of response

5. You want to fetch a list of users from an API in Astro frontmatter and display their names. Which approach correctly fetches and prepares the data for rendering?

---
// Option A
const res = await fetch('https://api.example.com/users');
const users = await res.json();
---


  {users.map(user => 
{user.name}
)}

hard

A. Fetch data in frontmatter but forget to parse JSON

B. Fetch without await, map users directly on Promise

C. Fetch with await, parse JSON, then map users in component

D. Use fetch inside component JSX without frontmatter

Solution

1. Step 1: Fetch and parse JSON in frontmatter

   Using await fetch and await res.json() gets the user list as an array before rendering.

2. Step 2: Map over users array in component

   Mapping users to list items displays each user name correctly in the rendered HTML.

3. Final Answer:

   Fetch with await, parse JSON, then map users in component -> Option C

4. Quick Check:

   Await fetch + parse + map users = correct [OK]

Hint: Await fetch and parse JSON before mapping data [OK]

Common Mistakes:

• Mapping over unresolved Promise instead of data array
• Fetching inside JSX causing runtime errors
• Not parsing JSON before using data