Postman vs ReadMe.io

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Postman
Postman

15.6K
12.3K
+ 1
1.7K
ReadMe.io
ReadMe.io

65
93
+ 1
70
Add tool

Postman vs ReadMe.io: What are the differences?

Developers describe Postman as "Only complete API development environment". Postman is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. On the other hand, ReadMe.io is detailed as "Beautiful documentation made easy". Collaborative Developer Hubs.

Postman can be classified as a tool in the "API Tools" category, while ReadMe.io is grouped under "Documentation as a Service & Tools".

Some of the features offered by Postman are:

  • Compact layout
  • HTTP requests with file upload support
  • Formatted API responses for JSON and XML

On the other hand, ReadMe.io provides the following key features:

  • Collaboration - Crowdsource your docs! Users can keep docs current by suggesting changes.
  • API Explorer - Let users play with your API right inside the documentation.
  • GitHub Sync - Keep auto-generated reference docs synced with your actual code.

"Easy to use" is the primary reason why developers consider Postman over the competitors, whereas "Great UI" was stated as the key factor in picking ReadMe.io.

PedidosYa, Movielala, and Webedia are some of the popular companies that use Postman, whereas ReadMe.io is used by UNION, ReadMe.io, and Codacy. Postman has a broader approval, being mentioned in 1725 company stacks & 2166 developers stacks; compared to ReadMe.io, which is listed in 33 company stacks and 4 developer stacks.

- No public GitHub repository available -
- No public GitHub repository available -

What is Postman?

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

What is ReadMe.io?

Collaborative Developer Hubs
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Postman?
Why do developers choose ReadMe.io?

Sign up to add, upvote and see more prosMake informed product decisions

Sign up to add, upvote and see more consMake informed product decisions

What companies use Postman?
What companies use ReadMe.io?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Postman?
What tools integrate with ReadMe.io?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Postman and ReadMe.io?
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
Insomnia REST Client
Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux.
Paw
Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code.
Apigee
API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world.
cURL
Used in command lines or scripts to transfer data. It is also used in cars, television sets, routers, printers, audio equipment, mobile phones, tablets, and is the internet transfer backbone for thousands of software applications affecting billions of humans daily.
See all alternatives
Decisions about Postman and ReadMe.io
Todd Gardner
Todd Gardner
President at TrackJS · | 4 upvotes · 72.5K views
atTrackJSTrackJS
Gatsby
Gatsby
Read the Docs
Read the Docs
ReadMe.io
ReadMe.io
GitHub Pages
GitHub Pages
Jekyll
Jekyll

We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

See more
Noah Zoschke
Noah Zoschke
Engineering Manager at Segment · | 28 upvotes · 168K views
atSegmentSegment
Swagger UI
Swagger UI
ReadMe.io
ReadMe.io
Markdown
Markdown
Postman
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
Jagdeep Singh
Jagdeep Singh
Tech Lead at ucreate.it · | 7 upvotes · 17.1K views
atucreateucreate
Postman
Postman

I use Postman because of the ease of team-management, using workspaces and teams, runner, collections, environment variables, test-scripts (post execution), variable management (pre and post execution), folders (inside collections, for better management of APIs), newman, easy-ci-integration (and probably a few more things that I am not able to recall right now).

See more
Nicholas Rogoff
Nicholas Rogoff
at Avanade UK Ltd. · | 7 upvotes · 72.1K views
atNHS Digital (NHS.UK)NHS Digital (NHS.UK)
Visual Studio
Visual Studio
Visual Studio Code
Visual Studio Code
Newman
Newman
Postman
Postman
Azure DevOps
Azure DevOps
Git
Git
jQuery
jQuery
JavaScript
JavaScript
Microsoft SQL Server
Microsoft SQL Server
C#
C#
.NET Core
.NET Core

Secure Membership Web API backed by SQL Server. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD.

We have .Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. For this service I opted to keep it as a classic WebAPI project and deployed to AppService.

  • Trusted Authentication Provider: @AzureActiveDirectoryB2C
  • Frameworks: .NET Core
  • Language: C# , Microsoft SQL Server , JavaScript
  • IDEs: Visual Studio Code , Visual Studio
  • Libraries: jQuery @EntityFramework, @AutoMapper, @FeatureToggle , @Swashbuckle
  • Database: @SqlAzure
  • Source Control: Git
  • Build and Release Pipelines: Azure DevOps
  • Test tools: Postman , Newman
  • Test framework: @nUnit, @moq
  • Infrastructure: @AzureAppService, @AzureAPIManagement
See more
Jason Barry
Jason Barry
Cofounder at FeaturePeek · | 4 upvotes · 38.9K views
atFeaturePeekFeaturePeek
Dropbox
Dropbox
Paw
Paw
Postman
Postman
Insomnia REST Client
Insomnia REST Client

We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

  • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
  • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
  • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

See more
Interest over time
Reviews of Postman and ReadMe.io
Review ofReadMe.ioReadMe.io

I cannot stress enough how important it is for companies to avoid Readme.io.

There is no accountability from their team when their service encounters serious errors. For weeks now, the service has been throwing internal server errors which were caught by monitoring tools.

In reaching out to readme.io support, the only information they ever gave was "Thank you" and a link to their status page. The status page does not reflect the fact the services is severely depredated and any further attempts over the past 14 days to reach support have been met with total silence.

Then there was an exchange with their CEO on Twitter who seemed like they may try to get us some sort of response or RFO, but that has also been met with silence after submitting exactly what was requested.

If you value the ability for your customers to reach your API Documents, then do not use readme.io.

README.IO DOES NOT CARE ABOUT YOU AS A CUSTOMER.

Review ofReadMe.ioReadMe.io

A pretty UI and the right combination of tools (tutorial section, API documentation, announcements) does not make up for consistently slow and buggy experience. As the amount of stored documentation grows, the app becomes more and more unreliable about saving changes, and for complex, in-depth documentation, the anchor tagging system is terrible, leading to false redirects. Multiple times, I have lost everything I've worked on, and the support service is terrible, even at the enterprise level. Other times, my changes are being saved, even though the app tells me they are not. I do not recommend this service for any company with lots of documentation.

Avatar of sergiotapia
Senior Software Engineer
Review ofPostmanPostman

If you're building an API service, this Chrome extension is a must-have. It'll let you ping your endpoints using a nice clean UI that's built right into Chrome. You can also share your previous requests - a simple way to 'document' your API if you're short on time.

Avatar of DaneLyons
Cofounder
Review ofPostmanPostman

If someone is having trouble shipping data to the Knowtify API, I almost always share my postman collection. Working through the issue from there is typically pretty easy.

Avatar of jgentes
Founder of StartupCommunity.org at The Social Business
Review ofPostmanPostman

Not much to say, it's the best free tool out there for testing APIs. Get it.

How developers use Postman and ReadMe.io
Avatar of shridhardalavi
shridhardalavi uses PostmanPostman

Postman is a powerful tool for performing integration testing with your API. It allows for repeatable, reliable tests that can be automated and used in a variety of environments and includes useful tools for persisting data and simulating how a user might actually be interacting with the system

Avatar of Scrayos UG (haftungsbeschränkt)
Scrayos UG (haftungsbeschränkt) uses PostmanPostman

We use Postman in conjunction with our universal REST-API "JCVortex". Postman makes testing edge-cases hassle-free and lets testing look easy. Postman was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

Avatar of Rashid Muhammad
Rashid Muhammad uses PostmanPostman

I use it for testing my Web Api. It's a easy tool for interacting with a RESTFul API and provides great tools for organizing requests. The Newman tool is great for allowing your tests to run in a CI/CD pipeline.

Avatar of Xpertz
Xpertz uses PostmanPostman

Used to test API endpoints and monitor API which also acts as an API heartbeat to keep functions alive in Google Cloud in order to avoid timeout responses to Slack.

Avatar of David Flynn
David Flynn uses PostmanPostman

We use Postman for all our API testing. Postman is invaluable. We would like to have a team licence so that we can use shared work spaces and test collections.

Avatar of SHOUTca.st
SHOUTca.st uses ReadMe.ioReadMe.io

Used for docs.shoutca.st + open source documentation of Cast.

How much does Postman cost?
How much does ReadMe.io cost?