It was around the 17th of August when a friend of mine, Yash, shared the link for the Keploy API Fellowship and suggested we join, since it was all about APIs. I was learning Android development at the time, and REST APIs kept showing up in almost every article and tutorial I read. I was curious about what they actually were and how they were built. After filling out the form and reading a little about Keploy, it was clear the program was about APIs and their testing, so I signed up.
Why an Android Learner Ends Up Caring About APIs
If you are building mobile apps, you run into APIs almost immediately. The app on the phone is only half the story. The other half lives on a server, and a REST API is the contract between the two: the app asks for data over HTTP, the server responds, and the screen updates. I had been consuming that idea without understanding it, which is exactly why a fellowship that started from first principles appealed to me.
Meeting the Mentors and the Peer Group
Early on I met the mentors and seniors: Hardik, Nishant, Ankit, and Sejal. They were excellent at explaining things, and the meetings were interactive rather than one-directional. They were always eager to help, and the peer group made the whole thing more fun. A good cohort matters more than people expect, because you learn as much from other participants’ questions as from your own.
What We Learned and Built
We covered a lot of ground, starting with the difference between HTTP and HTTPS and how requests and responses actually move across the web. From there we moved into building. We made a weather website that used a public API to fetch live data and display it, and we built a Superhero API in Go, among other small projects. Each one turned an abstract concept into something running in front of me.
The homework was the part that made it stick. Every assignment reused what we had learned in the previous sessions, so the ideas compounded instead of fading. Somewhere in that loop of learning and applying, my approach changed. I started reading the actual documentation and applying it directly to my own projects, which is a habit I have kept since.
Where This Leaves Me
From this fellowship my way of learning took a genuine turn. I would love to become a known and active member of the Keploy community, somewhere I can teach others what I know, take on new responsibilities, learn from my mistakes, and explore something new every day. If you are curious about how the record and replay approach to API testing fits into all of this, it is worth a look once you have the fundamentals down.
Frequently Asked Questions
What is the Keploy API Fellowship about?
It is a hands-on program focused on APIs and API testing. It covers the fundamentals, from how HTTP and HTTPS work to building and testing your own APIs, through interactive sessions and practical homework.
Do I need to know APIs before joining?
No. The fellowship starts from the basics, including what an API is and how requests and responses work. Curiosity and a willingness to do the homework matter more than prior experience.
What projects will I build?
Participants build small, practical projects such as a weather website that consumes a public API and a Superhero API written in Go, alongside homework that reinforces each session.
How did the fellowship change how I learn?
It moved me from passively following tutorials to reading documentation and applying it directly to my own projects, which made the learning far more durable.
