#error-message #grpc #standard-error #tonic #status #deprecated #details


Assets for implementation of the gRPC Richer Error Model with tonic

5 releases

0.3.2 Apr 6, 2023
0.3.1 Aug 18, 2022
0.3.0 Aug 17, 2022
0.2.1 Jul 13, 2022
0.2.0 Jul 12, 2022

#1407 in Network programming

Download history 23/week @ 2024-03-16 8/week @ 2024-03-23 59/week @ 2024-03-30 85/week @ 2024-04-06 113/week @ 2024-04-13 46/week @ 2024-04-20 22/week @ 2024-04-27 1/week @ 2024-05-04

95 downloads per month

MIT license


Important: This crate's functionality was incorporated into tonic-types and will be actively maintained there. This repository is no longer maintained.

Tonic Richer Error

Assets for implementation of the gRPC Richer Error Model with tonic.

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

Crates.io Documentation Crates.io

Examples | Website | Docs


The WithErrorDetails trait adds associated functions to tonic::Status that can be used on the server side to create a status with error details, that can then be returned to the gRPC client. 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

To build this crate you must have the Protocol Buffer Compiler, protoc, installed. Instructions can be found here.

tonic = "0.8"
tonic-richer-error = "0.3"


The examples bellow cover a basic use case. More complete server and client implementations can be found at the examples directory.

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

use tonic::{Code, Status};
use tonic_richer_error::{ErrorDetails, WithErrorDetails};

// ...
// 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_richer_error::WithErrorDetails;

// ...

// 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

Send different standard error messages

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 WithErrorDetails 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 WithErrorDetails::with_error_details_vec and WithErrorDetails::get_error_details_vec docs, and also the examples directory.

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


This project is licensed under the MIT license.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion by you, shall be licensed as MIT, without any additional terms or conditions.


~155K SLoC