Status

    • The Status type is a structured way to represent errors in various programming environments, including REST APIs and RPC APIs, and is used by gRPC.

    • Each Status message consists of three components: an integer error code ( code ), a developer-facing error message in English ( message ), and an optional list of objects ( details ) containing further error specifics.

    • Status utilizes a common error model that is further detailed in the Google API Design Guide for developers seeking more information and practical implementation advice.

    The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC . Each Status message contains three pieces of data: error code, error message, and error details.

    You can find out more about this error model and how to work with it in the API Design Guide .

    JSON representation 
     { 
 "code" 
 : 
 integer 
 , 
 "message" 
 : 
 string 
 , 
 "details" 
 : 
 [ 
 { 
 "@type" 
 : 
 string 
 , 
 field1 
 : 
 ... 
 , 
 ... 
 } 
 ] 
 }
    Fields
    code

    integer

    The status code, which should be an enum value of google.rpc.Code .
    message

    string

    A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
    details[]

    object

    A list of messages that carry the error details. There is a common set of message types for APIs to use.

    An object containing fields of an arbitrary type. An additional field "@type" contains a URI identifying the type. Example: { "id": 1234, "@type": "types.example.com/standard/id" } .
    Design a Mobile Site
    View Site in Mobile | Classic
    Share by: