HttpDash Download

Docs Sending and testing

gRPC requests

Create one with New → gRPC Request, or Add gRPC request on a collection or folder. It's saved like any request (shown as GRPC), so it lives in collections and syncs with your team.

  • Address: host:port, or a URL: grpcs:// and https:// mean TLS (port 443 by default), grpc:// and http:// mean plaintext. Settings → TLS can turn TLS on or off whatever the address says. {{variables}} work in the address, metadata and message.
  • Definitions, in the Definition tab:
    • Server reflection (the default): HttpDash asks the server for its services and messages (v1, or v1alpha for older servers). Reflected definitions are kept until you press the refresh button next to the method.
    • .proto files: add the files, and the folders their imports are relative to. Google's well-known types (google/protobuf/*.proto) are built in. The paths are of your computer, so teammates add their own.
  • Method: pick it next to the address; streaming methods say which way they stream. An empty message, or one still holding the last method's example, becomes the new method's example: every field with its default, nested messages included. Example fills it in again.
  • Message: JSON, with field names as in the .proto or in lowerCamelCase. A field the message doesn't have is an error rather than being dropped. 64-bit numbers are strings, so no digit is lost; enums are names; bytes are base64.
  • Metadata: the Metadata tab, plus the auth inherited from the collection or folder (Bearer, Basic, API key…) as authorization metadata. Keys ending in -bin take base64.
  • Calls of every kind:
    • Unary and server streaming: Invoke sends the message; every answer is listed as it arrives.
    • Client and bidirectional streaming: Start opens the call. Send messages one at a time with Send (Ctrl/Cmd+Enter), then End stream.
    • Cancel stops a call at any time.
  • Log: the call, response headers, every message sent (↑) and received (↓), and the final status (0 OK, 5 NOT_FOUND: …) with its trailers and time. Click a message to see it pretty-printed; a unary answer opens by itself.
  • Deadline: Settings → Deadline (ms), or the request timeout from Settings.
  • TLS: client certificates, trusted CAs (including the ones installed on your computer) and SSL verification from Settings apply as for HTTP.

Proxies and tunnels don't apply to gRPC yet. The Runner, Monitors, mock servers and Postman export skip gRPC requests, and a Flow step or AI agent that sends one is told it's sent from its own tab.

Edit this page on GitHub