Improve your skills by tackling a new Postman challenge for 15 days in a row.

Assess your Postman experience level

• Take the Postman skills quiz

Experience level for this test challenge

• Intermediate

How it works

1. Get the daily challenge: Fork the parent collection for each day to your own public Postman workspace.
2. Review the instructions: Read the corresponding collection documentation for instructions on how to complete each challenge. Additional resources are available if you want to dive deeper into any of the topics.
3. Check your solutions: When you think you've got it, validate your solution by following the instructions in the Submit your solution folder. For each day, you check your own work.

Watch this video for some 15-day-challenge tips:

Prerequisites

1. Sign in to Postman: Create a Postman account if you don't have one already, and log into Postman for the web in your browser. To use Postman in a web browser, download and run the Postman agent on your local machine to overcome cross-origin resource sharing (CORS) limitations. The agent is not the same as the app. On a Mac, you will see an icon for the Postman agent running in the status menu at the top right of your computer screen. On a Windows machine, the Postman agent icon displays in the system tray at the bottom right of your computer screen.
2. Create a public workspace: Create a new Postman workspace with visibility set to Public to show your work. Choose a unique name for your workspace to deter others from directly copying your answers.

What You'll Learn

• Basic testing skills like how to write and run API tests in Postman
• Higher-level testing skills like using variables, scripts, and automation
• Advanced testing skills like generating dynamic variables, using libraries and mock servers

What You'll Need

• A Postman Account

What You'll Build

• A public Postman workspace with collections, monitors, mock servers, code samples, and more.

Frequently Asked Questions

• How long does it take to complete the 15 days of Postman challenge? Plan to spend 5 to 45 minutes every day to explore the topic and dive deeper into the topics you find interesting. Go at your own pace. There is no penalty for taking longer. Note: if a very long period of time elapses from when you fork a challenge to when you submit the final solution, you may need to pull the latest changes to ensure the solution you submit is up to date.
• Do I need to complete all 15 challenges? You are welcome to dive into any of the topics that you find interesting. However, some challenges build on concepts and samples introduced in earlier challenges. So you will receive less guidance for concepts covered earlier in the series.
• I am new to code. Is this challenge for me? The challenges are designed for testers and suitable for novice testers. If you know basic software programming concepts and beginner JavaScript (or some other programming language), this challenge is for you. If you're an API professional, but don't identify as a tester, you may need to do extra research to complete some challenges.
• Do I need to create a public workspace?: Yes. The validation requires all of your work to be located in a public workspace. If you belong to your company's Postman team, your company may not want the public workspace to be listed under their public team profile. In this case, use your personal Postman account, or create a separate Postman account, to complete the challenge.
• I'm stuck. Can someone please help?
  • Re-read the instructions carefully, and check out the documentation and additional resources listed in the instructions.
  • Try submitting an incomplete solution locally to reveal clues in the test results.
  • Look for similar examples in the community forum.
  • If you're asking for help, try posting in the Training section of the community forum. Make sure to include a thorough explanation of your question, what you've tried already, and include a direct link to your own public workspace so others can see where you're stuck.

Learning Objectives

After completing this challenge, you'll be able to:

• Import data into Postman
• Send and retrieve data from an API
• Inspect API requests and responses
• Use collection variables to store data

Getting Started

1. Get the challenge: Fork the parent collection Day 01: API client to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder API client. Expand the context bar on the right to follow the instructions in the collection documentation. If you find it bothersome to navigate between the documentation while working in a different area of Postman, remember that you can open a new tab to keep your place in the documentation, and then switch between tabs.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Fork a collection
• View documentation
• Send a request
• Use variables

Additional resources

• Intro to APIs video series
• Postman API docs
• Initial vs Current Values for Variables video
• Create a public workspace docs
• Agent for the Postman web client video

Learning Objectives

• Configure request headers
• Explain version control in Postman
• Fork and merge changes into a collection
• Use environment variables to store data

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Fork a collection
• Send body data
• Use environments
• Configure request headers

Additional resources

• Version Control for Collections video
• How to use Postman environments video

Learning Objectives

• Inspect default console data
• Log data to the console
• Write a script

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Debug and log
• Script

Additional resources

• Debugging with the console video
• Powerful Debugging with the Postman Console blog
• How to use the Postman Console collection
• Import a HAR file in Postman video
• Reverse engineering a private API video
• Capture API calls with a proxy video

Learning Objectives

• Authorize API requests by using API key
• Use an authorization helper
• Explain inheritance regarding auth type
• Authorize API requests by using cookies

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Authorize requests
• Inheriting Auth Details video
• Securely using API keys in Postman blog

Additional resources

• Use cookies
• Sync cookies for authentication video

Learning Objectives

• Set and get variables using code
• Use variables to store and pass along data
• Run a collection or folder

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Defining variables
• Accessing variables
• Variable scopes
• Scripting in Postman
• Collection Runner

Additional resources

• 10 tips for working with variables blog

Learning Objectives

• Parse a response object
• Insert a test via snippet
• Write a custom Postman test
• Use API calls to replicate a user scenario
• Add multiple assertions to a test
• Explain how Chai.js BDD syntax is used in Postman

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Writing tests
• Test snippets
• Collection Runner
• Postman sandbox docs

Additional resources

• Test script examples in the docs
• Intro to writing tests - with examples sample collection
• Chai.js docs
• Continuous Quality webinar video
• Continuous Testing webinar video

Learning Objectives

• Write tests for request, folder, or collection
• Write dynamic tests using variables
• Run a collection locally using the collection runner
• Schedule a collection run on Postman Cloud
• Schedule a collection-based monitor on Postman Cloud

Getting Started

Fork the parent collection to your own workspace.

Concepts

• Write tests
• Collection Runner
• Schedule collection runs
• Schedule collection-based monitors

Additional resources

• Run collections on the command line with Newman docs
• Trigger runs with webhooks docs
• Log Response Data in Collection Runs video

Learning Objectives

• Write dynamic log statements
• Run collections from the command line
• Explain additional methods to output test results
• Set up and tear down state in tests

Getting started

Fork the parent collection to your own workspace.

Concepts

• Write tests
• Collection Runner
• Schedule collection runs
• Run collections on the command line with Newman docs

Additional resources

• Use custom reporters with Newman docs
• Newman with Docker docs
• Manage CLI environment variables video
• Write to your local file system blog
• Visualizing responses docs

Learning Objectives

• Update requests dynamically such as for pagination
• Write code to branch and loop API execution
• Set variables conditionally to keep track of data

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Variables
• Scripts
• Writing tests
• Building request workflows
• Running a collection

Additional resources

• Example in Postman Answers workspace
• Sending asynchronous requests

Learning Objectives

• Use external data files to pass Postman values
• Generate sample data dynamically
• Increase test scenarios

Getting started

Fork the parent collection to your own workspace.

Concepts

• Using dynamic variables
• Working with data files
• Running a collection

Additional resources

• Looping through a data file with the Postman collection runner blog
• Loop through a data file video
• How to break an API stream
• Unbreakable API code samples
• Big List of Naughty Strings

Learning Objectives

• Validate responses against a defined schema
• Explain the importance of schema validation
• Write a conditional test to validate various responses
• Write a negative test to validate an unsuccessful response

Getting started

Fork the parent collection to your own workspace.

Concepts

• Writing tests
• Validating responses

Additional resources

• ajv and other built-in libraries
• Validate using ajv code sample
• Validate data formats using JSON schema
• Validate API definitions docs
• Security warnings during API definition blog

Learning Objectives

• Use built-in libraries
• Visualize response data using Handlebars.js
• Define and reference external libraries
• Reuse test scripts and requests
• Send asynchronous HTTP requests from scripts

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Visualize responses
• Use external libraries
• Reuse test scripts and requests code samples
• Send HTTP request from scripts

Additional resources

• Handlebars.js docs
• Add external libraries code samples

Learning Objectives

• Use mock servers to prototype scenarios
• Explain consumer-driven contract testing using mocks
• Establish a process for snapshot testing using mocks
• Generate boilerplate code to replicate API calls

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Set up mock servers
• Generate code snippets

Additional resources

• Fake it till you make it: mocks for agile development blog
• Mock Servers Exploratory video
• Consumer-driven contract testing blog
• Snapshot testing for APIs using Postman blog

Learning Objectives

• Conditionally skip tests and requests
• Configure test retries and timeouts

Getting started

Fork the parent collection to your own workspace.

Concepts covered

• Writing tests
• Conditionally skip tests and requests
• Test retries and timeouts

Additional resources

• Ignore requests in a collection run code sample
• Ignore specific tests code sample

Learning Objectives

By the end of this challenge, you should have some experience with most of the following Postman testing skills. [insert link to quiz]

• Importing data into Postman
• Using variables to store and reuse data
• Writing Postman tests using snippets and Chai.js
• Writing custom tests using dynamic variables
• Generate sample data, variables, and logs dynamically
• Organizing multiple Postman tests by topic
• Passing the values to the runner through environment variables and data file
• Validate responses against a defined schema
• Selecting requests to run using command line arguments and runner settings
• Authentication using an API key
• Authentication using cookies
• Setting up and tearing down state in tests
• Using request and test retries
• Installing and using Newman for running collections from the command line
• Debugging unexpected API behavior
• Stubbing network calls using a mock server
• Recording network calls using the Interceptor
• Controlling the API workflow for branching and looping
• Visualizing response data
• Using external libraries
• Generate boilerplate code to replicate API calls
• Collaborating with team members to edit collections using version control
• Find answers to your Postman questions

If you feel shaky on any of these topics, now is a good time to refresh your learning before moving on.

Check your workspace for completeness

Make sure all of your tests are passing locally, and that you've completed the requirements. This includes all of the collections, mock servers, and scheduled collection runs required to complete the training.

If you need support figuring out how to complete the requirements, ask in the Postman community forum using the "training" category.

Don't stop now. You're on a roll! Check out some of our other learning labs, or learn how to test APIs in other protocols and patterns, like GraphQL, SOAP, gRPC, WebSockets, and more.

There's also a number of integrations that weren't covered in these lessons.

• Explain how Postman works with APM tools
• Explain how Postman works with source control technology
• Explain how Postman works with CI/CD platforms
• Explain how Postman works with API gateways
• Explain how Postman works with alerting and monitoring tools

Additional resources

• Postman Quick Reference guide community cheatsheet
• Community showcase with blog posts, tutorials, collections, and other really cool stuff by community members, just like you!
• Additional hands-on learning courses by Postman
• Videos including how-to, level ups, and exploratories
• Virtual learning webinars