Module
Module 3 of 6Lesson 2 of 2~16 min

Turning your requests into a tested collection

Lesson 2 of the module "Testing an API yourself" in the course "Design and test an API integration as a PM".

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to add tests to your requests, reuse a value from a response in the next request, organize a collection that also covers failure cases and replay it in one click.

Where it fits

Testing an API yourself

How can I check an API's real behavior myself, without writing code?

Lessons in this module

  1. Sending your first requests in Postman or Bruno
  2. Turning your requests into a tested collection (this lesson)

What you will learn in the course

This lesson is part of the course Design and test an API integration as a PM

  • Read a REST API's documentation (resources, endpoints, methods, parameters, JSON bodies, OpenAPI description) and extract what the integration needs.
  • Send, save and test requests in Postman or Bruno (collection, environments, variables, assertions) to check an API's real behavior.
  • Interpret status codes and error responses, and decide the product behavior (fix, retry, alert, inform the user).
  • Choose and specify the authentication method (API key, token, OAuth 2.0), the minimal permissions and the rules for managing secrets.
  • Specify pagination, rate-limit handling, webhooks and idempotency for an integration that withstands volumes, outages and duplicates.
  • Plan environments (sandbox, production), versions, breaking changes and deprecations in the spec and the test plan.
  • Write a complete integration spec, with a collection of tested requests, ready to be estimated by the team.

Related courses