Unary RPC
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://statuscodefyi.com/iframe/glossary/unary-rpc/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/glossary/unary-rpc/
Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/glossary/unary-rpc/)
Use the native HTML custom element.
The simplest gRPC pattern — a single request from the client receives a single response from the server, analogous to a standard HTTP request-response cycle. Unary RPCs are the most common pattern and the easiest to reason about for error handling and deadlines. The client blocks until the server responds or the deadline expires. All gRPC interceptors, deadlines, and retry policies apply to unary calls.