APIs are everywhere. This means there is a huge dependency on leveraging them to build various products. Whether your APIs are internal or external-facing, the importance of a proper testing process shouldn’t change. API Testing has reached stardom nowadays. And by now many would be familiar with the basics of API tests – for instance: what is API, what are status codes, etc. Rather than limiting the testing scope to cosmetic checks like verifying status code, verifying response headers, etc we as Testers should know the core principles and the important strategy to test APIs.

Apart from these basic validations, there are some interesting yet important areas to focus on in API Testing, away from the usual concepts. Although being an API Tester for 2 years, it took time for me to unlock these insightful areas in API Testing.

Now, what are those important areas that are often skipped? To rather frame it as pointers let’s put them as questions:

I uncovered the answers to these questions gradually in my API Testing journey, so here I’m to retrospect my study about API testing. Happy to demystify API Testing and share its insight with everyone.

Key Takeaways


Jency is an Ardent Software Tester and has been investigating the line between Software and Testing for the past 8+years. Her love affair with ‘Software Testing’ began years ago, starting from an ‘ETL Test Engineer’ to currently ‘Senior QA Engineer’ in the role of a passionate ‘API Tester’ at “Billennium IT Services (M) SDN. BHD.”. She loves to spend time exploring the concepts and interesting facts about Software Testing. She is fond of sharing her experiences by blogging and participating in tech communities. Jency is an ISTQB Certified Foundation Level and Agile Tester. Other interesting facts about Jency – MOM of a 3year old Superhero | Certified Mentor | Community Contributor | Occasional YouTuber.

LinkedIn: jency-stella