QueryUserByMobileAccount - Quick BI - Alibaba Cloud Documentation Center

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

quickbi-public:QueryUserByMobileAccount

get

*All Resource

*

None

Request syntax

POST  HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
MobileUserId	string	Yes	The bound mobile user ID. DingTalk: The unionId of the DingTalk account. WeCom: The userId of the WeCom account. Lark: The userId of the Lark account. Important The mobileUserId must be obtained by calling the relevant API operations of DingTalk, WeCom, or Lark.	sasda
MobileType	string	Yes	The bound mobile type. DingTalk: ding WeCom: corp_weixin Lark: feishu	ding

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	46e53***********270
Result	object	The user information bound to the third-party account.
BoundUserId	string	The Quick BI user ID of the bound account.	test
ThirdAccountName	string	The mobile account name.	test
Success	boolean	Indicates whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true

Examples

Success response

JSON format

{
  "RequestId": "46e53***********270",
  "Result": {
    "BoundUserId": "test",
    "ThirdAccountName": "test"
  },
  "Success": true
}

Error codes

HTTP status code	Error code	Error message	Description
400	Internal.System.Error	An internal system error occurred.	An internal system error occurred.
400	Invalid.Parameter.Error	The parameter is invalid:%s.	invalid parameter: ${0}.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.