> 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-101-with-postman.md).

# API 101 with Postman

Dear API enthusiasts, \
I hope you're doing awesome! <3\
\
I would like to express my deepest gratitude to all the API enthusiasts who attended API 101 in API Week. Your passion and enthusiasm for APIs were truly inspiring, and your willingness to learn and engage in discussions made the event a huge success. 🚀

<figure><img src="/files/4ZyXaMo698qXMMJolsmL" alt=""><figcaption><p>Kicstarting series of API Week</p></figcaption></figure>

The API 101 session experienced a challenging start as the first speaker faced technical issues due to a poor internet connection. Despite her best efforts, the speaker was unable to deliver her presentation seamlessly, as the network connection was unstable due to her travel. As a result, attendees found it challenging to follow along with the presentation, leading to confusion and disorientation. 😕

Nevertheless, the organizers took swift action, and  I took over the session and worked hard to compensate for the connectivity issues. I started by providing a brief overview of what APIs are and how they work, ensuring that everyone was on the same page. 😄

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><em>BEFORE</em></td><td></td><td align="center"><img src="/files/Z7IYBeUh3kyHViRpPcxo" alt=""></td></tr><tr><td align="center"><em>AFTER</em></td><td></td><td align="center"><img src="/files/KBlA2FbJfJBBcTTovtRV" alt=""></td></tr></tbody></table>

In my API session, I used a toy as an analogy to explain APIs. Like the Lego bricks of software development, APIs allow different software components to communicate and work together seamlessly, much like how the various parts of a toy work together to create a cohesive whole. By understanding this analogy and the basics of APIs, developers can build powerful and adaptable applications. 🧸

<div align="left"><figure><img src="/files/RPhPakArJXXNXx0778iw" alt=""><figcaption><p>Me: presenting toy as an analogy</p></figcaption></figure> <figure><img src="/files/PcU9EXkFTMd5PGe9UMG5" alt=""><figcaption><p>meme</p></figcaption></figure></div>

Then, the practical exercises began, and the new speaker, Pooja Gera was able to guide everyone through the exercises despite the internet connectivity issues. They provided clear explanations and easy-to-follow instructions, making it easy for attendees to create their own working APIs. 💖

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><em>PRESENTATION</em></td><td></td><td align="center"><img src="/files/7SbDO4waqssfqSbjqJhF" alt=""></td></tr><tr><td align="center"><em>PRACTICAL</em></td><td></td><td align="center"><img src="/files/xjdnGKQw8lFBFMp002Js" alt=""></td></tr></tbody></table>

Pooja was a standout speaker in the API session, delivering the practical part with skill and aplomb. Attendees were impressed with her ability to simplify complex concepts and explain them in a way that was easy to understand. Moreover, Pooja's interaction with the audience was excellent, she was attentive to their needs, and answered all questions with clarity and enthusiasm. Her positive attitude and engaging presentation style made the session enjoyable and memorable for all participants. Organizers were also impressed with her professionalism and expertise, and it was clear that Pooja was a valuable asset to the session. Overall, Pooja's contribution to the API session was a resounding success, and everyone appreciated her knowledge, talent, and approachable demeanor. 🥹 <3

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><em>SWAGS</em></td><td></td><td align="center"><img src="/files/gjqyeXlS3ErPzm48kPcF" alt=""></td></tr><tr><td align="center"><em>Q&#x26;A</em></td><td></td><td align="center"><img src="/files/HfFs0B6HewpM9yvATuRQ" alt=""></td></tr></tbody></table>

In the final segment of the API session, we assigned a challenge to the attendees, outlining the necessary details such as expected deliverables, submission procedures, evaluation criteria, and exciting giveaways for the top performers. Before concluding, we also facilitated a Q\&A session to address any concerns or questions that the participants had. We had promised to provide a comprehensive and informative session at the outset, and we ensured to keep that commitment by delivering an engaging and insightful presentation. The challenge was aimed at helping the attendees to apply the concepts learned during the session practically. By incorporating a Q\&A session, I provided an opportunity for the participants to clarify any doubts and ensured that they left with a clear understanding of the material covered. ✅

<details>

<summary>👉 Reminder: Challenge I      ( vvvvvimp.)</summary>

<img src="/files/TrDmElNpaT6Dkxi7uM9E" alt="" data-size="original">    Click [here](broken://pages/F6WbDsrFDBwnMnT0sBl3#week-long-tasks) for challenge yourself & win swags!

</details>

It was a pleasure to share our knowledge and insights with such a curious and engaged audience. We hope that the information and tools provided during API 101 will be helpful in your future API endeavors.

\
Thank you for your active participation and for being a valuable part of the Postman community. ✨\
\
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-101-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.
