GetLivyComputeToken - E-MapReduce - Alibaba Cloud Documentation Center

Retrieves a token for a Livy Gateway.

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

emr-serverless-spark:GetLivyComputeToken

get

*All Resource

*

None

Request syntax

GET /api/interactive/v1/workspace/{workspaceBizId}/livycompute/{livyComputeId}/token/{tokenId} HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
workspaceBizId	string	No	The ID of the workspace.	w-8adde60aa809701f
livyComputeId	string	No	The ID of the Livy Gateway.	lc-6mkvn01zrg8rqhhv
tokenId	string	No	The ID of the token.	lctk-xxxxxxxx
regionId	string	No	The ID of the region.	cn-hangzhou

Response elements

Element	Type	Description	Example
	object	Schema of the response
requestId	string	The ID of the request.	484D9DDA-300D-525E-AF7A-0CCCA5C64A7A
code	string	The response code. A value of 1000000 indicates that the request was successful. Other values indicate that the request failed. For more information about the error, see the message parameter.	1000000
message	string	The response message.	ok
data	object	The data returned.
tokenId	string	The ID of the token.	lctk-xxxxxxxxxx
name	string	The name of the token.	test
token	string	The content of the token.	d25561157a635bb
createdBy	string	The name of the user who created the token.	alice
createTime	integer	The time when the token was created.	1749456094000
expireTime	integer	The time when the token expires.	1749457994000
lastUsedTime	integer	The time when the token was last used.	1749456098000
autoExpireConfiguration	object	The information about token expiration.
enable	boolean	Specifies whether the token automatically expires. true: Yes. false: No.	false
expireDays	integer	The expiration period, in days.	7

Examples

Success response

JSON format

{
  "requestId": "484D9DDA-300D-525E-AF7A-0CCCA5C64A7A",
  "code": "1000000",
  "message": "ok",
  "data": {
    "tokenId": "lctk-xxxxxxxxxx",
    "name": "test",
    "token": "d25561157a635bb",
    "createdBy": "alice",
    "createTime": 1749456094000,
    "expireTime": 1749457994000,
    "lastUsedTime": 1749456098000,
    "autoExpireConfiguration": {
      "enable": false,
      "expireDays": 7
    }
  }
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.