Consume public APIs from the Postman API Network

Before you consume a public API, learn how to choose one from a verified team. A public API from a verified team offers you the best developer experience. You can then fork their elements to your own workspace and use them there. Remember to watch elements to get notified when there's a change.

Choose public elements

Postman recommends you choose a public API from a verified team. You can identify a verified team by its verification badge . If Postman verifies a team, it means Postman confirmed the following:

• The team owns the API and its services.
• The team actively maintains its public workspaces, and documents its collections well.
• The team's public APIs offer Guided Auth, which offers you the best developer experience.

It's safe to choose a public API from a non-verified team. If you choose an API from such a team, Postman recommends you go to the company's official website and review their official documentation. Then, compare their official URLs to the URLs they use in their public workspaces.

If a team isn't verified, it may mean the team isn't active in Postman, their collections aren't well-documented, or their verification is pending.

To learn more about the verification process, see Verify your team for the Postman API Network.

Use public elements

Once you've chosen a public API, Postman recommends you get started by forking one of the team's collections. Verified teams walk you through the process with great documentation. If you prefer, you can create the request yourself.

Whether you use Guided Auth or another method to authenticate, Postman recommends you store your authentication credentials in Postman Vault.

Similarly, you can copy a flow or create the flow yourself.

Watch public elements

You can watch public workspaces and collections to get notified about changes. To watch a workspace or collection, in the upper-right corner, select Watch.

To learn more, see Watch a workspace or Watch a collection.