- 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
Adding your API to the Network
Publishing your documentation to the API Network connects your API to the Postman community. You can publish docs to the network from any team collection—for individual collections that are not published via a team, you can instead add to the Postman templates.
Sharing your docs exposes your API to the millions of developers who use Postman, and lets others within the community learn from your projects. By publishing to the API Network, you share your API through a human-readable reference in the form of your docs—and an executable way to interact with your API endpoints inside Postman, via the embedded Run in Postman button.
Your docs can convey detailed guidance on how to make requests to your API endpoints, as well as the workflows required to integrate with your API in general. This provides the information—and actionable data—developers need to get started using your services.
When you add your API to the network it will be associated with your public team profile listing. You can set your profile up before publishing or Postman will generate one for you during publication and you can optionally customize it later.
To add an API to the network, you first need to document and publish a collection. You can share your docs to the API Network during the publishing process, by enabling Collection discovery and selecting Add to API Network.
If your collection is already published, you can make it discoverable by opening the published docs, opening the Published drop-down menu, and clicking Edit Published Documentation.
You can access your published docs from the Postman app (select the collection and click View in web), or from the web dashboard (navigate to Workspace > Collections and click the published collection title).
Click Allow Collection Discovery to set up your network listing.
Select Add to API Network.
Include the API Name, Summary, and Description—add the details potential users will need to know in order to find your API and figure out whether they want to use it. Your description can include markdown, and will automatically be populated from any description you already have included in your collection.
Select the categories that best describe your API and service. API consumers can choose categories to browse APIs in the network from the left sidebar in the Postman app and at explore.postman.com.
When you publish to the API Network, your API will be listed as part of your team profile. If you don't already have a team profile, Postman will automatically generate one when you publish. You can customize your profile at any time before or after publishing your API.
Use the Public Profile Settings link or navigate to your team profile settings to enable or customize the details consumers will see when your API is published and visible in the network.
Include a team name and description that will appear in your API Network listing. You can customize your profile URL, and add a logo and favicon in your Settings.
Once your team profile is set up any collection docs you publish will be associated with it. Click Publish Collection.
When people browse the API Network they will see your team profile listing, along with the APIs and templates you have published.
If you choose to disable your team profile, you won't be able to publish any new collections to the Postman API Network or templates, and any previously published collections will be unpublished.
You will see a link to your collection's published listing and team profile. You will also be able to find your listing in the Postman app using New > API Network or on the web.
Your team's API Network listing shows the number of imports for each of your APIs, with links to the documentation and Run in Postman button so that people can import your collection templates directly into the app to begin using your endpoints straight away.
Clicking the title of an API in the web listing of your team profile will open the listing page for that particular collection, showing the description, publisher details, imports, and linking to the documentation alongside Run in Postman for importing the collection directly.
Check out some tips for making the most of your network listing.