Latest Advancements to Postman’s gRPC Support
Tags: api, postman, news
Published: 2022-07-11 06:08:34

---
title: Latest Advancements to Postman’s gRPC Support
published: true
date: 2022-07-07 14:33:32 UTC
tags: api, postman, news
canonical_url: https://blog.postman.com/latest-advancements-to-postmans-grpc-support/
cover_image: https://dev-to-uploads.s3.amazonaws.com/uploads/articles/b0kpxpfrewceu69p14sb.jpeg
---

This article was written by [Sterling Ching](https://blog.postman.com/author/sterling-chin/).

It’s been almost six months since we released [support for gRPC in Postman](https://dev.to/jansche/postman-now-supports-grpc-47jm-temp-slug-314573 "https://blog.postman.com/postman-now-supports-grpc/"). Since then, we’ve been hard at work evolving the product into something that would be a true delight for the gRPC community. The community has been an enormous help by logging their [issues on GitHub](https://github.com/postmanlabs/postman-app-support/issues?q=is%3Aissue+label%3Agrpc+is%3Aopen "https://github.com/postmanlabs/postman-app-support/issues?q=is%3Aissue+label%3Agrpc+is%3Aopen") and [providing direct feedback](https://go.pstmn.io/grpc-feedback "https://go.pstmn.io/grpc-feedback") regarding pain points and feature requests. Thanks to everyone who has helped us on this journey!

Implementing real, first-class support for gRPC in Postman has been no small task. However, it’s just one of many new protocols that will be coming to the Postman API Platform.

In the latest release, we’ve unblocked many critical workflows that were previously a limiting factor for many of our users. First, our designer redesigned the gRPC interface. It’s now much more intuitive and easier to understand for first-time users. Second, all of Postman’s rich collaboration features are now available for gRPC just as they are for HTTP. And third, you can now save your multi-file Protobuf APIs in Postman’s cloud (we know _many_ of you were waiting for that!). We hope these changes, and more, will help provide a welcoming experience to gRPC newcomers and power users alike.

## The right tool for the job

The organizations that are adopting gRPC are strategically choosing it to solve service-to-service communication issues around performance and maintainability. For years, the web was primarily composed of HTTP with REST or SOAP.  As the web grew, so did the need for other protocols to help facilitate new uses. To build an [API-first world](https://api-first-world.com/ "https://api-first-world.com/"), we need support for more than just a single API protocol. This is why Postman engineering is placing an emphasis on [supporting any protocol](https://www.youtube.com/watch?v=VaiwEdXLjYE&t=2083s "https://www.youtube.com/watch?v=VaiwEdXLjYE&t=2083s"), including gRPC, [WebSockets](https://dev.to/arlemi/its-a-happy-birthday-postman-websocket-support-turns-1-39ii-temp-slug-2646498 "https://blog.postman.com/postman-websocket-support-turns-1/"), [GraphQL](https://blog.postman.com/postman-v7-2-supports-graphql/ "https://blog.postman.com/postman-v7-2-supports-graphql/"), and more.

Discovery drives adoption. That’s why we are actively working to provide not just client support, but clear documentation about gRPC’s use cases. We want to empower engineers, engineering and project managers, architects, designers, and more, to choose the right tool for the right job. If this is your first foray into gRPC, we recommend starting with the [introduction docs](https://grpc.io/docs/what-is-grpc/introduction/ "https://grpc.io/docs/what-is-grpc/introduction/") and understanding the [benefits of gRPC](https://cloud.google.com/blog/products/api-management/understanding-grpc-openapi-and-rest-and-when-to-use-them#:~:text=for%20doing%20that.-,gRPC%20benefits,-gRPC%20expresses%20an "https://cloud.google.com/blog/products/api-management/understanding-grpc-openapi-and-rest-and-when-to-use-them#:~:text=for%20doing%20that.-,gRPC%20benefits,-gRPC%20expresses%20an").

![Creating and sending a new gRPC request](https://blog.postman.com/wp-content/uploads/2022/07/New-SayHello-gRPC.gif)
_Creating and sending a new gRPC request_

## Collaborating with gRPC never looked so good

[Workspaces](https://blog.postman.com/public-workspaces-why-we-created-them-what-you-can-do/) have been a staple for Postman users for many years, enabling [better communication and collaboration](https://blog.postman.com/postman-workspaces/). We recently released the ability to save gRPC requests within collections, so teams can collaborate just as they have been with HTTP. But that’s not the end of the story. Aside from simply sharing a workspace or collection with the team, the ability to [fork](https://blog.postman.com/forking-merging-a-conflict-resolution-solution/) collections, as well as duplicate and move requests now ensures that the full cycle of collaboration is met. Also, if you need to communicate changes, doubts or issues around a request, you can [comment](https://blog.postman.com/new-inline-comments-make-collaboration-even-easier-in-postman/) on gRPC requests.

Additionally, you can share gRPC requests via a link. Simply click the link icon to copy a web URL to your clipboard and share to your heart’s content! You’ll share the whole request, including the URL, selected method, and attached message.

![Copying gRPC request link](https://blog.postman.com/wp-content/uploads/2022/07/copy-link1.gif)
_Copying gRPC request link_

## gRPC Reusability: unlocked

When importing your gRPC service definitions, you can now save _all_ relevant `.proto` files as a single API within the Postman cloud. This allows you to organize even your most complex gRPC APIs within Postman, enabling reusability and collaboration with the rest of your team.

To make it easier to get started, all new gRPC requests show recommendations of Protobuf APIs from within your workspace. Additionally, if your service supports gRPC server reflection, Postman will now _automatically_ detect it, and you’ll be able to send gRPC requests with only a single click—no Protobuf necessary!

## Learning from the past

We’ve all done something we wished we could go back in time to see again. For that reason, we added gRPC calls to the **History** tab. Now, builders and consumers can go back and revisit past calls, either to investigate an old bug or to remember what a successful call looked like.

![Showing off request history](https://blog.postman.com/wp-content/uploads/2022/07/history.gif)
_Showing off request history_

## Looking into the future

What we have now is a full picture of what a build cycle with gRPC looks like in Postman. From importing to saving, collaborating, forking and duplicating, re-using, and discoverability, the [whole API lifecycle](https://dev.to/jansche/the-8-point-api-lifecycle-blueprint-3op4-temp-slug-9748578 "https://blog.postman.com/api-lifecycle-blueprint/") can be achieved.

And we’re still working hard to provide even greater support for gRPC. This includes gRPC testing, which will give users the ability to write test scripts to validate responses from the server, including having access to our [commonly-used test code snippets](https://learning.postman.com/docs/writing-scripts/test-scripts/ "https://learning.postman.com/docs/writing-scripts/test-scripts/"). As engineers ourselves, we know you can’t overstate the value of the confidence we gain from writing tests for code and APIs alike. We’re also excited to be working on adding saved examples for gRPC, and automatic mock servers for all imported Protobuf APIs. Stay tuned for more updates. The future is bright with gRPC in Postman.

The post [Latest Advancements to Postman’s gRPC Support](https://blog.postman.com/latest-advancements-to-postmans-grpc-support/) appeared first on [Postman Blog](https://blog.postman.com).