> 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/foundation/intro-to-backend/week1/assignment.md).

# Assignment

## 1. Extend your webserver

In the session, you added plenty of useful routes to your API, but let's not stop there!

1. **Add 3 new routes**

   Think of 3 new useful routes yourself, and implement them.
2. **Extend the home route**

   Routes don't only have to return text or JSON, they can also return HTML content to be displayed in the browser.

   Update the `/` route to return a HTML page that fetches the count value from the `/user-count` route you've implemented previously. Style the HTML so it displays in a visually pleasing way. Now you've created a nice page to view the total number of users in your database!

## 2. Practice using Postman

Who doesn't love dogs? Ok... save the cat vs dog debate until after you've completed this exercise!

You'll be using the Dog API, where you can retrieve lots of doggy pictures. You can find the documentation on their website [dog.ceo/dog-api](https://dog.ceo/dog-api/).

You should create a collection in Postman, and set up requests for each of these tasks:

1. Get 5 random dog images (any breed)
2. List all the dog breeds
3. Get 3 dog images from the "beagle" breed
4. List all the sub-breeds of the poodle
5. Get all the dog images from the "toy poodle" sub breed

Share the link to your saved Postman Collection as part of submitting this assignment.


---

# 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/foundation/intro-to-backend/week1/assignment.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.
