Postman vs. Swagger UI



Hacker News, Reddit, Stack Overflow Stats

  • 1.31K
  • 673
  • 4.07K
  • -
  • 252
  • 1.9K

GitHub Stats

No public GitHub repository stats available
No public GitHub repository stats available

Description

What is Postman?

Postman is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.

What is Swagger UI?

Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation and sandbox from a Swagger-compliant API

Want advice about which of these to choose?Ask the StackShare community!

Pros

Why do developers choose Postman?
Why do you like Postman?

Why do developers choose Swagger UI?
Why do you like Swagger UI?

Cons

What are the cons of using Postman?
Downsides of Postman?

What are the cons of using Swagger UI?
No Cons submitted yet for Swagger UI
Downsides of Swagger UI?

Pricing

How much does Postman cost?
Postman Pricing
How much does Swagger UI cost?

Companies

What companies use Postman?
1975 companies on StackShare use Postman
What companies use Swagger UI?
185 companies on StackShare use Swagger UI

Integrations

What tools integrate with Postman?
13 tools on StackShare integrate with Postman
What tools integrate with Swagger UI?
5 tools on StackShare integrate with Swagger UI

What are some alternatives to Postman and Swagger UI?

  • Amazon API Gateway - Create, publish, maintain, monitor, and secure APIs at any scale
  • Apiary - Integrated API documentation, prototyping and testing
  • Paw - The ultimate REST client for Mac
  • Insomnia REST Client - The most intuitive cross-platform REST API Client 😴

See all alternatives to Postman

Latest News

Spotlight on Engineering: Kamalakannan
Read and write to REST-enabled databases
HarperDB uses Postman Pro as an IDE for their product
Related Stack Decisions
Noah Zoschke
Noah Zoschke
Engineering Manager at Segment ¡ | 24 upvotes ¡ 17030 views
atSegment
Swagger UI
ReadMe.io
Markdown
Postman
#QA
#Api
#Documentation

We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

See more


Interest Over Time