Skip to content
Download

gRPC

Discover or import services, send protobuf messages, and read responses.

gRPC requests target host:port or a grpc:// / grpcs:// style target. Kurlo can discover services by reflection when enabled, or use a selected .proto file with import paths.

The request body is JSON in protobuf JSON shape. Metadata lives in its own tab. The response panel separates:

  • Messages.
  • Response metadata.
  • Trailers.
  • Script output and test results.

gRPC supports pre-request/test scripts, environment variables, collection defaults, and runner reports.

A long server stream keeps its latest 500 messages in the Messages list and the response body. Messages keep their numbers, so the list then starts at the first one still kept; the response size still counts every message received.

For servers that require mutual TLS, set a Client certificate (mTLS) in the gRPC Settings tab. It works the same way as for HTTP — see Client certificate — and is sent whenever the call uses TLS (Use TLS on, or a grpcs:// target). Reflection uses the same connection, so it works against mTLS servers too.

To bring a native gRPC request from Postman, import its Postman v3 folder or *.request.yaml file. To take a native gRPC request into Postman, export its collection as a Postman v3 folder. Add the service’s .proto files in Postman if the server does not support reflection.

gRPC request with selected method and response messages