Prepare and verify your publisher team for the Postman API Network

As an API publisher on the Postman API Network, you can earn a Verified badge icon verification badge. API consumers trust content from verified publishers. To get verified, you must publish high-quality documentation and get-started guides, and set up authorization for your API consumers. When you're verified, it means Postman has confirmed your team is the authoritative owner of the public APIs hosted at your URLs. The badge also communicates that your API consumers can expect a quick path to their first 200 OK response.

If your team owns workspaces with collections that span multiple base URLs, you need to verify at least one domain from endpoints in your collections and ensure high-quality content.

You can apply and earn your verification badge by completing the tasks outlined in the following sections.

Start your application

To start your application, do the following:

  1. Navigate to the Postman API Network landing page. If you haven't started your verification application, you'll see a Get Verified link under the Publisher section on the left sidebar. Click the link to start your application.
  2. You can also start your application by accessing your publisher profile from the Postman API Network landing page. Click User icon Profile, then click the Not Verified label under your profile picture.
  3. On the self-serve verification landing page, click Continue to start your application.

Verify your team's identity

To verify your team's identity, do the following:

  1. If you haven't already, start your application.
  2. Click Identity.
  3. Verify your domain. To learn more, see Set up Guided Auth for public APIs in Postman.
  4. Add at least one team admin with a work email from a verified domain.
  5. Add at least two team members with work emails from a verified domain.

Prepare your profile

To prepare your team profile, do the following:

  1. If you haven't already, start your application.
  2. Click Publisher settings and profile.
  3. Add your official website and social media links.
  4. Add your logo for faster recognition and a background image to reinforce your brand.
  5. Include a detailed description of your API to help users understand what they can achieve when they use your API.
  6. Add a tagline and include a display name that helps consumers recognize you.
  7. Add a custom Postman domain to publish your API documentation.

Prepare your workspace

To prepare your workspace, do the following:

  1. If you haven't already, start your application.
  2. Click Workspaces.
  3. You must make at least one workspace public. Add summaries and descriptions to your public workspaces. To learn more, see Prepare your public workspace for the Postman API Network
  4. Give your assets and team unique names to help API users find you.
  5. Add summaries and descriptions to your collections to make them searchable. To learn more, see Prepare your public collections for the Postman API Network
  6. Organize your Collections by using folders to group requests by type or use case. Add descriptions to folders to help users navigate your API.
  7. Add descriptions and response examples to your requests.

Review your content for usability

To review your content, do the following:

  1. If you haven't already, start your application.
  2. Click Usability.
  3. Add a Run in Postman button to link your external sites to Postman.
  4. Review the usability checklist to make sure your API has been tested and that you are satisfied with the quality of the content.

You can complete the tasks at your own pace. The progress indicator shows you how close you are to meeting the requirements. When you’ve completed all the tasks, click Submit for review on the bottom right of the screen. Once Postman approves your request, you’ll see a verified badge on your profile.

If your team has already applied, you won't be able to apply again. Instead, you'll see the status of your application: Submitted, Under Review, Approved, or Declined.

Last modified: 2025/06/16