Welcome to my recap of the Keploy API Fellowship Program. Over six short days the fellowship took me from knowing very little about APIs to building and testing my own, and I want to walk through exactly what each day looked like, in case you are thinking about applying. First, a genuine thank you to team Keploy for selecting me. The experience was full of learning, and just as valuable, it introduced me to a community of people I am still connected with.
What the Keploy API Fellowship Is
The Keploy API Fellowship is a short, hands-on program that teaches the fundamentals of APIs and API testing through daily sessions and small projects. There is no heavy prerequisite. If you can write a little JavaScript and are willing to experiment, you can follow along. Each session builds on the last, so by the final day you have gone from the basic question of how an API works to shipping a working service of your own. The format leans on live orientation, guided builds, and mentor support rather than passive lectures.
My Six Days in the Fellowship
Day 1: Orientation and Meeting the Community
Day one was the orientation session. Most of it was about getting oriented to the program and, more importantly, meeting the other participants and mentors. I walked away with new connections before we had written a single line of code, which set the tone for the rest of the week.
Day 2: How APIs Actually Work
Day two covered the basics of APIs: what an API is, how one system requests data from another, and how APIs help manage and move that data between a client and a server. Having a clear mental model here made everything that followed much easier, because every project afterward was really just a different application of that same request and response idea.
Day 3: Building With a Public API
Day three was about public APIs, the openly available services anyone can call. We built a weather web app that pulls live data from a public weather API and displays it in the browser. This was the first app I had ever built using an API, and seeing real data appear on the page from a remote service was the moment the concept clicked.
Day 4: Creating Our Own API
On day four we moved from consuming an API to building one. We created a Movies API that reads movie data from a JSON file and serves it to the web, built with Node and Express. Writing the endpoints myself, rather than just calling someone else’s, made the request and response cycle feel concrete.
Day 5: Docker and Keploy
Day five introduced two tools I had not used before: Docker and Keploy. Docker packages an application and its dependencies so it runs the same way anywhere. Keploy was the highlight. It generates test cases and data mocks automatically by capturing the calls you make to your API through Postman or any other API client, so you get a working test suite without writing tests by hand. For someone new to testing, watching tests appear from real traffic was genuinely surprising. If you want to see how that works in practice, the API testing side of Keploy is the best place to start.
Day 6: Shipping a Ninja API in Go
The final day, day six, was about Go. We built a Ninja API in Go that served data much like the Movies API, and after a week in Node I came away thinking Go was actually the easier of the two to reason about for this kind of service. Ending the program by writing in a new language felt like proof of how much ground we had covered.
What I Took Away
By the end I had picked up a stack of new skills: APIs, public APIs, building my own endpoints, Docker, Keploy, and a first taste of Go. Just as valuable was learning how to learn this kind of material, moving from watching a session to reading a little documentation and trying it myself. A large part of why the week worked was the mentors. Thank you to Hardik Kumar, Nishant Mishra, Ankit Kumar, and Sejal Jain for the patient and warm guidance throughout.
Frequently Asked Questions
What is the Keploy API Fellowship?
It is a short, hands-on fellowship that teaches API fundamentals and API testing through daily sessions and small guided projects, supported by mentors from the Keploy team.
Do I need prior experience with APIs to join?
No. The program starts from the basics of how an API works and builds up gradually. A little familiarity with JavaScript helps, but the early sessions assume you are new to APIs.
What will I build during the fellowship?
Over the program you build several small projects, including a weather app using a public API, your own API served from a JSON file with Node and Express, and a service written in Go. You also generate automated API tests using Keploy.
How long is the fellowship?
This cohort ran over six days of sessions, moving from orientation on day one to building and testing your own API by day six.
