Protocols
Thunder Client goes beyond REST. You can send HTTP and GraphQL requests, watch live Server-Sent Events streams, exchange messages with WebSocket servers, and call gRPC services. Every request type is saved in collections and syncs with Git, just like any other request.
Choose a Request Type
| Request type | Communication | Use it for |
|---|---|---|
| HTTP | One request, one response | REST APIs, GraphQL, webhooks, file uploads |
| Server-Sent Events | One request, a stream of events from the server | Live feeds, progress updates, notifications, streamed AI responses |
| WebSocket | A connection that stays open, with messages in both directions | Chat, multiplayer, live dashboards, trading and pub/sub APIs |
| gRPC (Beta) | Typed calls defined in a .proto file: unary or streaming | Microservices and internal APIs built on Protocol Buffers |
Create a Request
- HTTP — In the sidebar, click New Request.
- Other types — Click the arrow next to New Request and select Event Stream Request, WebSocket Request, or gRPC Request (Beta).
Feature Support
Most features work across all request types. The table below shows where they differ.
| Feature | HTTP | SSE | WebSocket | gRPC |
|---|---|---|---|---|
| Environment variables | ✓ | ✓ | URL, headers, auth | — |
| Headers / Metadata | ✓ | ✓ | ✓ | ✓ |
| Auth | All types | All types | Basic, Bearer | Basic, Bearer |
| Tests | ✓ | ✓ | — | — |
| Pre-requests and scripts | ✓ | ✓ | — | — |
| Code Snippet | ✓ | ✓ | — | — |
Last updated on