> For the complete documentation index, see [llms.txt](https://program.hackyourfuture.dk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://program.hackyourfuture.dk/course-content/backend/node/week1/session-materials/03-routing.md).

# 3. Routing

## End goal structure

The end goal of the exercise is to implement the following routes:

* `GET /api/snippets` to get a list of snippets
* `GET /api/snippets/:id` to get a single snippet

## Create Snippets router

We will create the snippet routes in a different file, `api/snippets.js`, which will export an [Express router](https://expressjs.com/en/starter/basic-routing.html).

That will look something like this:

```js
// Contents of api/snippets.js

import express from "express";
const router = express.Router();

// GET /api/snippets
router.get("/", async (request, response) => {
  // TODO
  console.log("Hello from Snippets");
});

// TODO: GET /api/snippets/:id

export default router;
```

## Add the router to the main server

Next thing in the setup is to actually use the router we're exporting from `api/snippets.js`. Inside `app.js`, below setting up Express, add your new snippets router:

```js
import snippetsRouter from "./api/snippets.js";

app.use("/api/snippets", snippetsRouter);
```

## Test the app

Run the main app. Does you console log `Hello from Snippets` on <http://localhost:3000/api/snippets>?

## End file structure

At this point verify that your project structure looks like this:

* api
  * snippets.js
* app.js
* package.json


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://program.hackyourfuture.dk/course-content/backend/node/week1/session-materials/03-routing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
