> For the complete documentation index, see [llms.txt](https://aminoxix.gitbook.io/api-week/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aminoxix.gitbook.io/api-week/api-103-with-postman.md).

# API 103 with Postman

Dear API Evangelist 🫡,\
Hope you're in the building.

<figure><img src="/files/utaeVEh1Wtq3FKVEKlYM" alt=""><figcaption></figcaption></figure>

We kicked off API 103 with an exciting session where I had the pleasure of hosting and speaking to our enthusiastic audience. The presentation included a series of slides that covered theoretical aspects of the client-side and server-side folders, which are combined as a monorepo in practice. I was thrilled to interact with the audience members who joined us on the YouTube live stream, and their engagement helped make the session even more dynamic.

<div><figure><img src="/files/soAgSoqVwUsLPH5YsXe2" alt=""><figcaption><p>API 102 -> API 103</p></figcaption></figure> <figure><img src="/files/EjIN5ZTXwvnBODdA9wgb" alt=""><figcaption><p>monorepo code tree</p></figcaption></figure></div>

Basant Barupal, an exceptional live programmer, took on the challenge of building a web application using the workflow that we introduced in API 102. Despite the challenges of live programming, Basant's dedication paid off and we were able to develop an impressive Spotify song recommender app using Tailwind CSS. The application was deployed on the `railway.app`, which added to the excitement of the event.

<div><figure><img src="/files/O4wJ6O7LNAgYcnEiTLNN" alt=""><figcaption><p>started with the express boilerplate</p></figcaption></figure> <figure><img src="/files/vfCLJSwNhutWWaGPsjjI" alt=""><figcaption><p>to getting our first data</p></figcaption></figure></div>

<div><figure><img src="/files/BRIopgWgYOqMmIYFeWmu" alt=""><figcaption><p>got the recommendation songs data on server-side</p></figcaption></figure> <figure><img src="/files/Z6R53I8G2ziX2MvgyYWt" alt=""><figcaption><p>finally, got client-side data as well 🥳</p></figcaption></figure></div>

We also used TailwindCSS to beautify our application:

<div><figure><img src="/files/Qi09AVKz2lJb2KGMmIUM" alt=""><figcaption><p>cdn link for express app</p></figcaption></figure> <figure><img src="/files/VNRi4DWnHEhjkThyrGHx" alt=""><figcaption><p>our final app! <span data-gb-custom-inline data-tag="emoji" data-code="1f389">🎉</span></p></figcaption></figure></div>

In the final stages of our project, we encountered a roadblock when attempting to deploy our Express app on `Vercel`. After realizing that this platform would not meet our deployment needs, we quickly made the decision to switch to `railway.app`  our hosting solution. As committed, we are happy to share the link to our completed project with you below.

<div><figure><img src="/files/u4BlLa1cFPZ6gcMSvauk" alt=""><figcaption><p>using railway.app</p></figcaption></figure> <figure><img src="/files/7AgetYaXhNDX5FpFtz01" alt=""><figcaption><p>Successful Deployment <span data-gb-custom-inline data-tag="emoji" data-code="303d">〽️</span></p></figcaption></figure></div>

:link: [https://spotify-song-recommender-production.up.railway.app](https://spotify-song-recommender-production.up.railway.app/) (Just need to click on :zap:Generate Link in `Settings` tab)

It was truly gratifying to see the joy on the faces of our participants as they built a web application that met all the required specifications. Although it was challenging to stay engaged throughout the session, the effort was well worth it.

Congratulations to all the participants who learned and built something meaningful. Now, it's time to share your creations with the world. This is where Challenge III comes in - I explained the details in the video and provided an image below for reference.

<figure><img src="/files/o8aQHjDUP3PBDBeIeIEc" alt=""><figcaption><p>Let's compete!</p></figcaption></figure>

Thank you for sticking with us until the end of the session. Pat yourself on the back, you're now an API-ready developer!

Best Regards,\
**aminos & Team**\
Postman Student Leader


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aminoxix.gitbook.io/api-week/api-103-with-postman.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
