gRPC requests

Choose Add gRPC in a collection or a section.

Address and TLS

Use grpc:// for plaintext or grpcs:// for TLS. For grpcs://, Codestamp uses the CA certificates and client certificates from Settings. gRPC always accepts TLS 1.2 and later, and it does not use a proxy.

Load services

Codestamp can read services and methods in two ways:

• Server reflection, trying v1 first and then v1alpha.
• A .proto file that you pick in the system file dialog. Imports are read from the same folder, and Google’s built-in types are available.

Codestamp reads a .proto file only when you pick it in the dialog on this computer. The path stays on your device and is not shared with a team.

Call a method

All four kinds work: unary, server stream, client stream and bidirectional. Choosing a method fills a JSON message template with every field, as an array for client streams.

• You can add metadata and auth (Bearer, Basic, API key in a header, or OAuth 2.0).
• {{variable}} works in the address, the metadata and the message.
• The reply shows the gRPC status (for example 5 NOT_FOUND), the message, the headers and the trailers separately.

Limits

• A server stream shows at most 200 messages.
• A message can be up to 32 MB.
• Binary metadata (-bin) is not supported yet.
• Run all and export skip gRPC requests, and say so.