CapabilityCallbackResponse

  • The CapabilityCallbackResponse object, which is deprecated, provides information about a user's RBM capability and is received by an agent in the data field of a message object from a Google Pub/Sub subscription.

  • The CapabilityCallbackResponse includes fields such as requestId, phoneNumber, rbmEnabled, features, and status to detail the user's RBM capabilities.

  • The status field, an object of type Status, contains an error code, error message, and error details if the capability check fails.

  • The Status type follows a logical error model suitable for different programming environments, including REST and RPC APIs, and is used by gRPC.

  • The Status object includes code (an integer status code), message (a developer-facing error message), and details (a list of messages carrying error details).

The RBM capability of a user. This response is the result of a capability.requestCapabilityCallback request from the agent.

The CapabilityCallbackResponse appears in the "data" field of the "message" object that the agent receives from its Google Pub/Sub subscription. The "data" field is a base64-encoded string that the agent must decode to match the CapabilityCallbackResponse structure. Deprecated: No longer used.

JSON representation 
{
  "requestId": string,
  "phoneNumber": string,
  "rbmEnabled": boolean,
  "features": [
    enum (Feature)
  ],
  "status": {
    object (Status)
  }
}
Fields
requestId

string

The UUID assigned by the agent to the capability.requestCapabilityCallback request.
phoneNumber

string

Phone number of the user in E.164 format.
rbmEnabled

boolean

Whether the user is capable of participating in RBM conversations with agents.
features[]

enum (Feature)

List of all RBM features which are supported for this phone number
status

object (Status)

Status of the response. If the capability check fails, includes error messages.

Status

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" }.