gRPC Support
Proto management, server reflection, and unary and streaming calls.
gRPC Support
Bifurc supports saved gRPC request definitions, proto-aware exploration, and server reflection.
What you can do
- save gRPC requests with service, method, metadata, and message body
- import and store
.protofiles - discover services and methods through server reflection
- detect unary, server-streaming, client-streaming, and bidirectional workflows
- keep protocol definitions and request examples under workspace version control
Typical workflow
- Open Requests and create a gRPC request
- Create a request tab
- Enter the server address
- Import a proto file or use server reflection
- Select a service and method
- Fill in the JSON request body and metadata
- Invoke the method and inspect the response
Important architecture note
gRPC relies on HTTP/2 framing, so it is not routed through the proxies the way REST, GraphQL, and SOAP traffic is. Bifurc calls gRPC services directly from the request editor, and gRPC mocking is not supported.
Good use cases
- local development against unstable gRPC backends
- validating request and response shapes from proto contracts
- exercising streaming methods against a local service