new_releases 更新:查看
版本说明,了解新功能和产品动态。
CapabilityCallbackResponse
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
用户的 RBM 功能。此响应是代理发出的 capability.requestCapabilityCallback 请求的结果。
CapabilityCallbackResponse 会显示在代理从其 Google Pub/Sub 订阅接收的“message”对象的“data”字段中。“data”字段是一个 base64 编码的字符串,代理必须对其进行解码才能与 CapabilityCallbackResponse 结构匹配。已弃用:不再使用。
JSON 表示法 |
{
"requestId": string,
"phoneNumber": string,
"rbmEnabled": boolean,
"features": [
enum (Feature )
],
"status": {
object (Status )
}
} |
字段 |
requestId |
string
代理为 capability.requestCapabilityCallback 请求分配的 UUID。
|
phoneNumber |
string
用户的电话号码,采用 E.164 格式。
|
rbmEnabled |
boolean
用户是否能够与代理进行 RBM 对话。
|
features[] |
enum (Feature )
相应电话号码支持的所有 RBM 功能的列表
|
status |
object (Status )
响应的状态。如果功能检查失败,则包含错误消息。
|
状态
Status
类型定义了适用于不同编程环境(包括 REST API 和 RPC API)的逻辑错误模型。此类型供 gRPC 使用。每条 Status
消息包含三部分数据:错误代码、错误消息和错误详细信息。
如需详细了解该错误模型及其使用方法,请参阅 API 设计指南。
JSON 表示法 |
{
"code": integer,
"message": string,
"details": [
{
"@type": string,
field1: ...,
...
}
]
} |
字段 |
code |
integer
状态代码,应为 google.rpc.Code 的枚举值。
|
message |
string
面向开发者的错误消息(应采用英语)。任何向用户显示的错误消息都应进行本地化并通过 google.rpc.Status.details 字段发送,或者由客户端进行本地化。
|
details[] |
object
包含错误详细信息的消息列表。有一组通用的消息类型可供 API 使用。 可以包含任意类型字段的对象。附加字段 "@type" 包含用于标示相应类型的 URI。示例:{ "id": 1234, "@type": "types.example.com/standard/id" } 。
|
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThe CapabilityCallbackResponse indicates a user's RBM capability and is received by agents via a Pub/Sub subscription, base64-encoded in the "data" field of the message object.\u003c/p\u003e\n"],["\u003cp\u003eThis response includes details such as the \u003ccode\u003erequestId\u003c/code\u003e, \u003ccode\u003ephoneNumber\u003c/code\u003e, \u003ccode\u003erbmEnabled\u003c/code\u003e status, and a list of \u003ccode\u003efeatures\u003c/code\u003e supported by the phone number.\u003c/p\u003e\n"],["\u003cp\u003eThe response also contains a \u003ccode\u003estatus\u003c/code\u003e object, which details the response status, and includes error messages if the capability check failed.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eStatus\u003c/code\u003e object adheres to the gRPC logical error model, containing an error \u003ccode\u003ecode\u003c/code\u003e, an error \u003ccode\u003emessage\u003c/code\u003e, and an array of error \u003ccode\u003edetails\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe error details can contain a type identification and specific fields, as well as the actual error messages.\u003c/p\u003e\n"]]],[],null,["# CapabilityCallbackResponse\n\n| This item is deprecated!\nThe RBM capability of a user. This response is the result of a capability.requestCapabilityCallback request from the agent.\n\nThe 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.\n\n| JSON representation |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ``` { \"requestId\": string, \"phoneNumber\": string, \"rbmEnabled\": boolean, \"features\": [ enum (/business-communications/rcs-business-messaging/reference/rest/v1/phones/getCapabilities#Feature) ], \"status\": { object (/business-communications/rcs-business-messaging/reference/rest/v1/CapabilityCallbackResponse#Status) } } ``` |\n\n| Fields ||\n|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `requestId` | `string` The UUID assigned by the agent to the capability.requestCapabilityCallback request. |\n| `phoneNumber` | `string` Phone number of the user in E.164 format. |\n| `rbmEnabled` | `boolean` Whether the user is capable of participating in RBM conversations with agents. |\n| `features[]` | `enum (`[Feature](/business-communications/rcs-business-messaging/reference/rest/v1/phones/getCapabilities#Feature)`)` List of all RBM features which are supported for this phone number |\n| `status` | `object (`[Status](/business-communications/rcs-business-messaging/reference/rest/v1/CapabilityCallbackResponse#Status)`)` Status of the response. If the capability check fails, includes error messages. |\n\nStatus\n------\n\nThe `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](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details.\n\nYou can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).\n\n| JSON representation |\n|------------------------------------------------------------------------------------------------------|\n| ``` { \"code\": integer, \"message\": string, \"details\": [ { \"@type\": string, field1: ..., ... } ] } ``` |\n\n| Fields ||\n|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `code` | `integer` The status code, which should be an enum value of `google.rpc.Code`. |\n| `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](/business-communications/rcs-business-messaging/reference/rest/v1/CapabilityCallbackResponse#Status.FIELDS.details) field, or localized by the client. |\n| `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\" }`. |"]]