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

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 the first 29 days, you will be checking your own work.
4. Claim your badge: For the final challenge, submit your final solution to the Postman team. Successfully completing all 30 challenges allows you to join the leaderboard and claim your 30 days of Postman badge.

Watch this video for some 30-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. Every day, fork a new challenge from the parent workspace to your own, and work through the day's challenge. Change the name of your public workspace to deter others from directly copying your answers.

What You'll Learn

• Basic development skills like how to send and authorize API requests
• Higher-level development skills like using variables, tests, and scripts
• Advanced development skills like visualizing data and generating dynamic requests

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 30 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 30 challenges? Completing all 30 challenges is required to claim your 30 days of Postman badge. You are welcome to dive into any of the topics that you find interesting. However, some challenges build on concepts 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 developers and suitable for novice developers. 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 developer, you may need to do extra research to complete some challenges.
• 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, 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.

1. Get the challenge: Fork the parent collection Day 01: Fork a collection to your own public workspace.
2. Read the documentation: In your fork, select the first folder Fork a collection. 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

• Forking a collection
• Viewing documentation
• Sending a request

Additional resources

• Version Control for Collections video
• Fork vs import tiktok

1. Get the challenge: Fork the parent collection Day 02: Collections and environments to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation. Remember, if you find it bothersome to navigate between the documentation while working in a different area of Postman, 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

• Adding requests
• Creating environments
• Postman API

Additional resources

• Postman Environments: How to Control Access to Variables, Workflows, and More blog
• Initial vs Current Values for Variables video
• Collections and environments tiktok

1. Get the challenge: Fork the parent collection Day 03: Add request details to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Sending body data
• Configuring request headers

Additional resources

• Upload a File via POST Request video
• API requests tiktok

1. Get the challenge: Fork the parent collection Day 04: Authorization to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Postman API
• Authorizing requests

Additional resources

• Inheriting Auth Details video
• Securely using API keys in Postman blog
• Authorization tiktok

1. Get the challenge: Fork the parent collection Day 05: Variables to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variable scopes
• Defining variables

Additional resources

• 10 tips for working with variables blog
• Variables tiktok

1. Get the challenge: Fork the parent collection Day 06: Tests to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Writing tests
• Test snippets

Additional resources

• Test script examples in the docs
• Intro to writing tests - with examples sample collection
• Chai.js docs
• Tests tiktok

1. Get the challenge: Fork the parent collection Day 07: Debugging to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Debugging and logs

Additional resources

• Debugging with the console video
• Powerful Debugging with the Postman Console blog
• How to use the Postman Console template
• Debugging tiktok

1. Get the challenge: Fork the parent collection Day 08: Run a collection to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Collection Runner

Additional resources

• Log Response Data in Collection Runs video
• Run collections tiktok

1. Get the challenge: Fork the parent collection Day 09: Scripting to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Scripting in Postman
• Building workflows

Additional resources

• Test script examples
• Scripting tiktok

1. Get the challenge: Fork the main collection Day 10: Mock services to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Setting up mock servers

Additional resources

• Fake it till you make it: mocks for agile development
• Mocks sample collection
• Mock servers tiktok

1. Get the challenge: Fork the parent collection Day 11: Monitoring from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Monitoring APIs and websites

Additional resources

• Using Postman to water my plants tutorial
• Analyzing with reports docs
• Postman API Monitoring Examples workspace
• Monitoring tiktok

1. Get the challenge: Fork the parent collection Day 12: Postman API to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Postman API

Additional resources

• Postman API documentation collection
• How to Get Started With the Postman API blog
• APIs tiktok#

1. Get the challenge: Fork the parent collection Day 13: Newman from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Scripts
• Writing tests
• Running collections on the command line with Newman

Additional resources

• Newman on GitHub
• Newman on npm
• Newman tiktok

1. Get the challenge: Fork the parent collection Day 14: OAuth from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• OAuth 2.0
• Variables
• Scripts
• Writing tests

Additional resources

• OAuth 2.0 examples
• OAuth 2.0: Implicit Flow is Dead, Try PKCE Instead blog
• Generate Spotify Playlists using a Postman Collection blog
• OAuth tiktok

1. Get the challenge: Fork the parent collection Day 15: Write to file from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• pm.sendRequest() to send asynchronous requests
• Write to your local file system using a Postman Collection blog

Additional resources

• Newman write to file code sample
• Write responses to file template
• Write to file tiktok

1. Get the challenge: Fork the parent collection Day 16: Pagination from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Pre-request and Test Scripts
• Writing tests
• Building request workflows
• Running a collection

Additional resources

• Pagination tiktok

1. Get the challenge: Fork the parent collection Day 17: Visualizations from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Visualizing responses

Additional resources

• Visualizer demo video
• Postman visualizer: More than meets the eye blog
• Graphing COVID Time Series Data Using Chart.js tutorial
• Visualizing Open Brewery Data with Bootstrap tutorial
• Visualization tiktok

1. Get the challenge: Fork the parent collection Day 18: API specifications from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Importing API specifications
• Using the API Builder

Additional resources

• How Postman Uses the OpenAPI Specification blog
• API specifications tiktok

1. Get the challenge: Fork the parent collection Day 19: GraphQL from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Querying with GraphQL

Additional resources

• GraphQL demo video
• Working with GraphQL template
• REST, SOAP, GraphQL — Gesundheit!
• GraphQL vs REST: Overview
• Public GraphQL APIs
• GraphQL tiktok

1. Get the challenge: Fork the parent collection Day 20: Documentation from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Documenting your API

Additional resources

• The Good Documentation checklist
• The Ultimate API Publisher's Guide
• Documentation tiktok

1. Get the challenge: Fork the parent collection Day 21: WebSockets from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Using WebSocket Requests
• Websockets tiktok

Additional resources

• WebSocket Requests video

1. Get the challenge: Fork the parent collection Day 22: Public profile from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.

Concepts covered

• Making your profile public
• Commenting on collections

Additional resources

• Public Profiles video
• Comments video
• Public profile tiktok

1. Get the challenge: Fork the parent collection Day 23: Data files from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Working with data files

Additional resources

• Looping through a data file with the Postman collection runner blog
• Loop through a data file video
• Data files tiktok

1. Get the challenge: Fork the parent collection Day 24: Using libraries from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Dynamic variables using faker library
• Using external libraries

Additional resources

• Using libraries tiktok

1. Get the challenge: Fork the parent collection Day 25: Dynamic request bodies from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Scripts
• Using dynamic variables
• Sending asynchronous requests
• Writing tests

Additional resources

• Example in Postman Answers workspace
• Dynamic requests tiktok

1. Get the challenge: Fork the parent collection Day 26: Parse HTML response from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Scripts
• Using external libraries
• Writing tests

Additional resources

• Example in Postman Answers workspace
• Check for Broken Links on Your Website Using a Postman Collection blog
• Parse HTML tiktok

1. Get the challenge: Fork the parent collection Day 27: Scenario testing from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Scripts
• Writing tests

Additional resources

• How to break an API livestream
• How Secure are your APIs? livestream
• Acing your API tests — what you need to know for test automation blog
• Scenario testing tiktok

1. Get the challenge: Fork the parent collection Day 28: UI testing from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Variables
• Scripts
• Writing tests

Additional resources

• UI Testing with Postman blog and code samples
• UI testing tiktok

1. Get the challenge: Fork the parent collection Day 29: Webhooks from the main workspace to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit your solution and follow the instructions in the documentation to validate your solution.

Concepts covered

• Set up integrations to receive alerts
• Postman API

Additional resources

• Custom webhook integrations
• Webhooks tiktok

1. Get the challenge: Fork the parent collection Day 30: Submit for badge to your own public workspace.
   
2. Read the documentation: In your fork, select the first folder. Expand the context bar on the right to follow the instructions in the collection documentation.
3. Submit your solution: Select the second folder Submit for badge and follow the instructions in the documentation to validate your solution.

This tutorial was a hands-on introduction to Postman for developers. To see what else you can do with Postman, check out the following resources:

• Additional hands-on learning courses by Postman
• Other opportunities to earn badges from Postman
• Videos including how-to, level ups, and exploratories
• Virtual learning webinars

Or explore the following topics:

• For API testing professionals: 15 Days of Postman - for Testers test challenge
• API-first design and development: OpenAPI 3.0: From Idea to Implementation video