#grpc #error-message #protobuf #rpc #grpc-client #grpc-server #client-server


A collection of useful protobuf types that can be used with tonic

14 releases (8 breaking)

0.11.0 Feb 8, 2024
0.10.2 Sep 28, 2023
0.9.2 Apr 17, 2023
0.9.0 Mar 31, 2023
0.1.0 Jul 8, 2020

#541 in Web programming

Download history 24235/week @ 2024-02-26 21836/week @ 2024-03-04 22994/week @ 2024-03-11 19358/week @ 2024-03-18 18611/week @ 2024-03-25 17174/week @ 2024-04-01 21905/week @ 2024-04-08 22795/week @ 2024-04-15 23694/week @ 2024-04-22 20403/week @ 2024-04-29 29548/week @ 2024-05-06 25260/week @ 2024-05-13 26580/week @ 2024-05-20 18965/week @ 2024-05-27 30687/week @ 2024-06-03 24107/week @ 2024-06-10

100,705 downloads per month
Used in 4 crates (3 directly)

MIT license

12K SLoC


A collection of useful protobuf types that can be used with tonic.

This crate also introduces the StatusExt trait and implements it in tonic::Status, allowing the implementation of the gRPC Richer Error Model with tonic in a convenient way.


Useful protobuf types are available through the pb module. They can be imported and worked with directly.

The StatusExt trait adds associated functions to tonic::Status that can be used on the server side to create a status with error details, which can then be returned to gRPC clients. Moreover, the trait also adds methods to tonic::Status that can be used by a tonic client to extract error details, and handle them with ease.

Getting Started

tonic = <tonic-version>
tonic-types = <tonic-types-version>


The examples bellow cover a basic use case of the gRPC Richer Error Model. More complete server and client implementations are provided in the Richer Error example, located in the main repo examples directory.

Server Side: Generating tonic::Status with an ErrorDetails struct

use tonic::{Code, Status};
use tonic_types::{ErrorDetails, StatusExt};

// ...
// Inside a gRPC server endpoint that returns `Result<Response<T>, Status>`

// Create empty `ErrorDetails` struct
let mut err_details = ErrorDetails::new();

// Add error details conditionally
if some_condition {
        "description of why the field_a is invalid"

if other_condition {
        "description of why the field_b is invalid",

// Check if any error details were set and return error status if so
if err_details.has_bad_request_violations() {
    // Add additional error details if necessary
        .add_help_link("description of link", "https://resource.example.local")
        .set_localized_message("en-US", "message for the user");

    let status = Status::with_error_details(
        "bad request",
    return Err(status);

// Handle valid request
// ...

Client Side: Extracting an ErrorDetails struct from tonic::Status

use tonic::{Response, Status};
use tonic_types::StatusExt;

// ...
// Where `req_result` was returned by a gRPC client endpoint method
fn handle_request_result<T>(req_result: Result<Response<T>, Status>) {
    match req_result {
        Ok(response) => {
            // Handle successful response
        Err(status) => {
            let err_details = status.get_error_details();
            if let Some(bad_request) = err_details.bad_request() {
                // Handle bad_request details
            if let Some(help) = err_details.help() {
                // Handle help details
            if let Some(localized_message) = err_details.localized_message() {
                // Handle localized_message details

Working with different error message types

Multiple examples are provided at the ErrorDetails doc. Instructions about how to use the fields of the standard error message types correctly are provided at error_details.proto.

Alternative tonic::Status associated functions and methods

In the StatusExt doc, an alternative way of interacting with tonic::Status is presented, using vectors of error details structs wrapped with the ErrorDetail enum. This approach can provide more control over the vector of standard error messages that will be generated or that was received, if necessary. To see how to adopt this approach, please check the StatusExt::with_error_details_vec and StatusExt::get_error_details_vec docs, and also the main repo's Richer Error example directory.

Besides that, multiple examples with alternative error details extraction methods are provided in the StatusExt doc, which can be specially useful if only one type of standard error message is being handled by the client. For example, using StatusExt::get_details_bad_request is a more direct way of extracting a BadRequest error message from tonic::Status.


~91K SLoC