Production Environments

Machine readable environments for APIs allow for abstracting away common elements of an API production environments from the definition of each API, allowing different environments to be paired with collections for each API at design, develop, and build time.

Does this provide what you need? Let us know by submitting issue!

A production environment is a set of variables you can use in your Postman requests. You can use production environments to group related sets of values together for use across individual, or many different collections. Environments help you abstract away secrets, tokens, and other data that you will need to use across different collections while working with different APIs. You can think of environments as a mini key-value store that you can apply to collections, but then also store data pulled from collection runs, persisting data across many different API requests. It is common for collection run results to be stored within environments, paginated data, and other results from API workflows and automation, making environments a pretty robust way to persist valuable data across API consumption.

Related Links


Blueprints

Return to Main Page

This provides a link back to the home page if you need it.