- Installation and updates
- Sending your first request
- Creating the first collection
- Navigating Postman
- Keyboard Shortcuts
- Postman account
- New button
- Troubleshooting In-app Issues
- Customizing Postman
- Find and Replace
- Troubleshooting API requests
- Debugging and logs
- Authorizing requests
- Capturing HTTP requests
- Generate code snippets
- Making SOAP requests
- Working with Tabs
- Using GraphQL
- Visualize API responses
- Intro to collections
- Creating collections
- Sharing collections
- Managing collections
- Requesting access
- Using Markdown for descriptions
- Data formats
- Working with OpenAPI
- Commenting on collections
- Version Control for Collections
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Working with data files
- Running multiple iterations
- Building workflows
- Sharing a collection run
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Viewing documentation
- Authoring your documentation
- Publishing your docs
- Custom documentation domains
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Pricing for monitors
- Troubleshooting monitors
- FAQs for monitors
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Introduction to APIs
- Managing APIs
- Sharing APIs and managing roles
- The API Workflow
- Validating Elements Against Schema
- Versioning APIs
- Reporting FAQs
- Viewing and analyzing APIs
- Intro to Workspaces
- Creating Workspaces
- Managing Workspaces
- Using Workspaces
- Sharing collections in Workspaces for version 5
- Viewing changelogs and restoring collections
- What is Postman Pro
- Purchasing Postman Pro
- Upgrading to Postman Pro from a trial team
- Team Settings
- Changing your plan
- Managing your team
- Migrating to Postman v7
- Roles and permissions
- Intro to Enterprise
- Purchasing Postman Enterprise
- Running Postman monitors using static IPs
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Audit logs
- Publishing API documentation
Publishing your docs
You can publish your API documentation to make it available for public viewing by anyone who has the link. Published documentation allows anyone who wants to learn how to use your API to view detail on endpoints, including parameters, request and response bodies, and example code.
Your public documentation will always display up-to-date content representing the current state of your collection. You don’t need to repeat the publication flow each time you want to update your documentation.
You can publish documentation for collections that you created or have permission to edit.
- Sharing your public docs
- Publishing and unpublishing
- Next steps
You can publish docs from an existing private documentation page or from the collection in the Postman app.
To publish from your collection's private documentation in the web browser, select a version and click Publish.
To publish from the collection in the Postman app, select the collection in Collections, open the actions menu (...), and choose Publish Docs.
Any confidential information in your environment, such as passwords and access tokens may become publicly visible when you publish your docs. Remove all sensitive information from the environment before you publish.
In the Publish Collection page, you can configure how you want your public docs to appear.
- Select a collection version to publish.
- Select an environment to populate variables in your published documentation.
You can preview your documentation before publishing it.
With a Postman Pro or Enterprise account, you can opt to use a custom domain for your public documentation site.
You can configure the style of your public docs by selecting colors for the top bar, sidebar, and highlights. Try making changes and preview to see how your docs will appear when published.
You can customize the style of your public docs by adding a team name and logo via your team settings if you have admin access. Your logo will replace the Postman logo in your team's published docs—updated logo images may take a few minutes to appear.
To share your API documentation with your users and the wider Postman community, enable Collection discovery by toggling the switch.
- Choose Add to API Network to feature your docs in the Postman publisher network.
- Choose Add to Postman Templates to share your collection with the Postman community and make it discoverable via the app.
You can only add to API Network when publishing from a team. You can configure your team profile by clicking Public Profile Settings, enabling your profile, and filling out your team details for display.
Your team profile can include a name, description, custom URL, and logo.
Add listing details for your public documentation, including name, summary, description, and relevant tags.
If you do not want to make your docs discoverable at this time, you can go ahead and publish then add them to the API Network or Postman Templates later.
Once you have your publish settings complete, click Publish Collection to make your docs public.
You will see a confirmation that your docs are public together with a link you can share.
You can unpublish your docs at any time by clicking Unpublish.