Postman 3.0: A whole new experience to supercharge your API workflow

We released Postman 2.0 just a couple of months ago. Since then, we have had thousands of users sign up for our Sync service for individual users, backed up more than 60,000 collections with more than 6 million requests in just a few weeks!

Even before we launched 2.0, the team has been hard at work in reimagining what our users can do with Postman. One thing that was clear to us is that Postman has grown way beyond from just being a REST client. While that’s something that will always be core to what Postman helps developers do, the problems our users are solving with Postman are much bigger. We talked to hundreds of teams over the past few months.

They are documenting APIs, integrating collections with build systems, distributing APIs and even monitoring APIs with a combination of Postman, Interceptor, and Newman.

While re-designing Postman, our core goal has been to make developers fasters at every step of the API development workflow. We took the first step with 2.0 when we launched Postman Sync – more on this in a bit, and from today onwards we have started rolling out Postman 3.0.

With Postman 3.0, you get:

Amazing new experience: The most visible change that you would see is the shiny new interface! We have re-designed the app from scratch. And it’s not just the UI. You will notice improvements in almost every workflow.

postman-2

Faster Sync performance: We have a blazing fast new Sync algorithm. Along with that, We have migrated to AWS from Linode in this new update. Our infrastructure will scale automatically along with server load. Subscribing to collections, receiving updates, and even first time syncing would be instantaneous.

Collection Browser: You can browse collections in an expanded view next to the sidebar. No more searching through static API doc pages for countless hours! All changes are synced across your team so you are always up to date.

Tabbed browsing: Work on multiple requests in parallel! Tabs will take your productivity to another level.

Screen Shot 2015-05-28 at 1.24.52 PM (2)

Code generator: Generate code snippets in more than 15 languages by hitting the “Code” button.

Smoother UI performance: We have made tons of improvements in the interface layer to make Postman render at 60 FPS. Along with this, We have migrated all code rendering to AceEditor. This enables Postman to render thousands of lines of code without any hit in performance.

Better search: Searching through responses is now way easier thanks to AceEditor. You can jump to occurences and even use regular expressions.

Team Sync

Postman Sync for teams gives you the ability to collaborate between your team members in real-time. We have been in private beta for a while and now we are opening up the beta to everyone. We had a stellar private beta with more than 80 companies helping us clean up the rough edges!

Postman Sync for teams gives you:

  1. Real-time sharing between team members
  2. API directory to browse your team’s collections
  3. Access control for APIs (editable and read-only modes)
  4. Automatic versioning and undo (coming soon)

For the full list of features, check out our beta page at beta.getpostman.com/intro. Pricing plans start at $49/month for up to 10 users. If you are a smaller team, do email us at help@getpostman.com.

Pulling off something of this complexity would have been impossible without the support of our investors, Nexus Venture Partners, who have seeded us with a cool 1 million dollars. You can read the full announcement on TechCrunch.

We are more excited than ever in building Postman. There is a lot for us to do. The problems with API workflow exist for developers, small teams to big enterprises. Email us for suggestions and do follow us on Twitter

23 thoughts on “Postman 3.0: A whole new experience to supercharge your API workflow”

  1. Cools stuff, but the colours look a little bit weird, blue next to green and orange. But hey, I'm not a designer.

    1. I agree. I also do not like the new layout. Everything is just too big. Also, once I send a request, I only see the response. The original request is now hidden. Maybe I am missing something, but this change doe snot look good to me. I like the previous, more minimalist view better.

      1. I tend to agree with everything is too big.
        I know that with all new UIs users need some adjustment period and I like the new features, but this new "bigness" is definitely a downside on smaller screens.

      2. +1 with not hiding the original request once you get the response. At least make this optional in settings.

  2. Always good to see progress. First thing I notice though is that is urls in json responses are not clickable anymore. I would like to see that back.

    Also I'm a bit disappointed on the pricing for team sync. We bought 8 licenses some time ago, based on the 'Only $9.99 for a single license. Free upgrades for life' statement. After buying the jetpacks I was a bit let down by the team feature, but had good hopes on upgrades. Now it seems the teamfeatures I'm looking for will cost a lot more. Instead of the onetime $80, it will be $600 a year. I understand making money is neccessary for continuation, but this difference is too much (at least for us).

    Nevertheless, keep up the good work

    1. Hi Chris,

      Jetpacks were meant to be client side updates which we can support without any server costs. Even now any client side update we push as part of Jetpacks is going to be free. We had to push the 'Jetpacks for Team' feature because users wanted the licenses in bulk and also manage them on an ongoing basis. (We tried doing this manually but was just not sustainable).

      However, real-time Sync is a completely different service with infrastructural and maintenance costs. A ton of other features are going to be part of the service and we'll have more announcements on the blog soon.

      – Abhinav

      1. Hi Abhinav, could you address Chris' first comment though about no longer showing clickable links within the response? The lack of this functionality prevents effective use of postman for hypermedia APIs.

  3. I am also concerned with the Save feature. If I enter an endpoint and save it to a collection then go to another endpoint and try to save that one I have to select the down arrow and choose saveas or it will overwrite my previous saved URL.

    I don't like this. If the URL is different then it should save a new one automatically. If it is preexisting URL then it should overwrite…in my opinion.

  4. I like the new layout and tabs are indeed great. My biggest problem though is the incredibly small scroll area when trying to scroll up and down in the sidebar. It is only a couple of pixels wide, so scrolling is very hard.

  5. Where did the preview feature go??? It's nearly impossible to debug requests without knowing what is being sent.

      1. There's a button labelled " below the Send button. This supports HTTP, CURL and other languages.

  6. I am just throwing it out there: would be cool to have a feature like sql transactions, so you can undo all your changes from a collection. I really have no idea how one could implement this.

  7. Postman is great and easy to use.
    However since the version 3.0, it becomes a separate window which does not share the chrome browser session anymore. In 2.0 i can login to some site and make rest call with the session info in postman, the new version seems to be not working.

    Please advise.

      1. Can you please explain with more details how to do it? I need 2 things that I was able to do on Postman 2.0:
        1) To send xdebug headers with Xdebug Helper plugin button
        2) To use the same browser session, instead of starting a new isolated session in postman 3 app.

  8. Can I download any 3.x version ? I just updated to 4.1.2 and all collections stoped from working! I cannot log in anymore in some sites I had stored!

Leave a Reply

Your email address will not be published. Required fields are marked *