Check LLM Dataset & Theme Permissions for RAM Users - Quick BI - Alibaba Cloud - Quick BI

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:QueryLlmCubeWithThemeListByUserId

get

*All Resource

*

None

Request syntax

POST  HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
UserId	string	Yes	User ID.	adsdasd-***********-123wdasd

Response elements

Element	Type	Description	Example
	object
RequestId	string	Request ID.	2EE822B***************F-F5B42DDADC12
Result	object	List of datasets and analysis themes.
CubeIds	object	Dataset map. key - Dataset ID value - Dataset name
	string	JSON object of the dataset.	"4d93*****0-9614-c97adea37911": "common*值"
ThemeIds	object	Analysis theme map. key - Analysis theme ID value - Analysis theme name
	string	JSON object of the analysis theme.	"9aefb3**********75abecbe": "www*******eeee"
Success	boolean	Whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true

Examples

Success response

JSON format

{
  "RequestId": "2EE822B***************F-F5B42DDADC12",
  "Result": {
    "CubeIds": {
      "key": "\"4d93*******0-9614-c97adea37911\": \"common***值\""
    },
    "ThemeIds": {
      "key": "\"9aefb3************75abecbe\": \"www*********eeee\""
    }
  },
  "Success": true
}

Error codes

HTTP status code	Error code	Error message
400	Internal.System.Error	An internal system error occurred.
400	ApiUser.Not.Exists	The specified user does not exist.
400	UserRoleConfig.NotContain.Function	The user %s does not have permission to operate.
400	RobotNl2sql.Moudle.NotPurchase	Please purchase Nl2sql module first.
400	Invalid.User.Organization	The user is not in your organization.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.