Get the daily challenge: Fork the parent collection for each day to your own public Postman workspace.
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.
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.
Claim your badge: For the final challenge, submit your final solution to the Postman team. Successfully completing all the challenges allows you to claim your 15 days of Postman badge.
Watch this video for some 15-day-challenge tips:
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.
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
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? Completing all the challenges is required to claim your 15 days of Postman badge. 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.
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.
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.
If your question is related to the administration of this badge (e.g. not a technical Postman question), you can ask for guidance in the Training section of the community forum.
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
Get the challenge: Fork the parent collection Day 01: API client to your own public workspace.
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.
Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.
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 successfully earned your badge, 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