Postman

Postman gives API teams a request client, shared collections, test scripts, documentation workflows, and automated collection runs.

Visit official website

Published Updated

CategoryTesting & QA
AccessSee vendor
PricingFreemium
APISee vendor
Overview

What is Postman?

Postman starts with an API request: a developer sets the endpoint, method, authorization, and payload, then inspects the response. Collections group related requests with examples, documentation, variables, and scripts, making an API workflow shareable with other developers. The current product also supports broader design and testing workflows; the useful starting point is a maintained collection that reflects the live API.

Read the full overview

Sources checked 27 September 2026: Postman overview and collections documentation.

Why teams use it

Key capabilities

  • Request client: construct and inspect supported API calls.
  • Collections: organize requests, examples, scripts, and documentation.
  • Variables and environments: reuse requests against different targets.
  • Collection runs: execute saved requests and tests manually or in automated workflows.
Core areas

Keep credentials out of shared examples, document expected status and response data, and review tests when the API contract changes. A collection with only successful sample requests is a reference, not a complete regression suite.

Positioning

Postman is an API development workspace rather than a guarantee that an API is correct. It is especially useful when a team needs reproducible requests and shared expectations for responses. Tests still need meaningful assertions, stable test data, and integration with the team's delivery process.

Why it matters

Postman can give developers and integrators a common, executable description of API behavior. Its current documentation was checked 27 September 2026. Adoption figures and claims of universal protocol support were removed because neither is needed to explain the workflow.

Deployment & technical details

Technical details

Access
See vendor
Source model
Other license
Founded
2012
Headquarters
San Francisco, USA
Pricing model
Freemium
API
Not specified
Check with the publisher

Official resources

Before you shortlist

What to verify for your environment

Start from the users, systems and operating responsibilities the tool needs to support.

  • Confirm current features, licensing and support terms with the publisher.
  • Validate deployment, data location, access control, backup and recovery requirements.
  • Test integrations, export paths and a representative operational workflow before committing.
Community experience

Reviews of Postman

No published reviews yet.

Loading review form…