Kreya VS grpcurl

Looks very nice; I've also given up with Postman. gRPC support would probably get Bruno into my daily workflow immediately. I spent a couple hours in Postman trying to get gRPC to work and could not- the .proto files were never used successfully, and I had better experiences with Kreya [0] and grpcui [1].

[0] https://kreya.app/

Kreya [1] can do that. It is even optimized for it, so that diffs should be perfectly readable.

[1] https://kreya.app

As one of the creators, I can recommmend https://kreya.app. It is not open source (like Postman), but has a strong focus on privacy and also stores the data locally.

As it has more powerful features (IMO) than most alternatives listed here, I am a little disappointed that it isn't mentioned more often.

There is also https://kreya.app, which has more features, but is closed-source

Given the recent update[0] pushed by the Insomnia team I am now looking for alternatives.

For now the best alternative I've found is Bruno[1]. But sadly it does not support gRPC.

Does anyone have a better solution?

These are some options I've looked into:

- https://hoppscotch.io/

- https://hurl.dev/

- https://recipeui.com/

- https://kreya.app/

- https://github.com/flawiddsouza/Restfox

[0] - https://github.com/Kong/insomnia/issues/6585

[1] - https://github.com/usebruno/bruno

If you need gRPC, I can recommend https://kreya.app/

I like Kreya (kreya.app), but I am biased, since I am one of the creators :)

Have you tried Kreya? While it does not support all of the many features of Postman, it has some innovative features. While also being web-based, it uses the native WebView of the OS, resulting in less RAM-usage than Electron based apps.

grpcurl

The API server will be built and start running on port 50051. You can test the functionality using a gRPC client of your choice like grpcurl or Postman.

> What is the ubiquitous utility for interacting with gRPC? We have curl for REST. What is openAPI of gRPC?

grpcurl[1] combined with gRPC server reflection[2]. The schema is compiled into the server as an encoded proto which is exposed via server reflection, which grpcurl reads to send correctly encoded requests.

[1] https://github.com/fullstorydev/grpcurl

The whole idea behind the post is that accessing the gRPC service with regular tools is impossible. To test, we need a dedicated tool nonetheless. I found grpcurl. Let's install it and use it to list available services:

gRpcurl is a cool little tool to look at btw. Had to use it at my job before. Can call a gRPC via a curl like command. Regular curl doesn't support HTTP2. Had to use TLS with some tokens even. But you can reference a local .proto(gRPC protobuf file for the call) and make things easier for yourself if you hate reading instructions on command line args like I do.

A simple GRPC client built using grpcurl.

Try testing with grpcurl, using the -H or -rpc-header flags to set the appropriate header.