ListHpoTrials - Platform For AI - Alibaba Cloud Documentation Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Returns all the trials for the specified experiment ID.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
paiautoml:ListHpoTrials	list	*HpoExperiment `acs:paiautoml:{#regionId}:{#accountId}:hpoexperiment/{#HpoExperimentId}`	none	none

Request syntax

GET /api/automl/v1/hpo/experiment/{ExperimentId}/trials HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
ExperimentId	string	No	The ID of the HPO experiment.	abcde
PageNumber	integer	No	The page number to return. Pages start from 1. You can use this parameter to search for HPO experiments.	1
PageSize	integer	No	The number of entries per page.	10
SortBy	string	No	The basis for sorting.	GmtCreateTime
Order	string	No	The order of specific fields of results in a paged query (ascending or descending). Default value: ASC. ASC Ascend DESC Descend	ASC

Response parameters

Parameter	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	3F190916-B3E5-5D1E-AD0C-35C0DF105F51
Code	string	The internal error code. This parameter is returned if an exception occurred.	INVALID_USER_OR_EXP
Message	string	The error message. This parameter is returned if an exception occurred.	Missing 'user_id' in request.
TotalCount	integer	The total number of entries returned. By default, this parameter is not returned.	5
Trials	array	Data structs of the trial.
Trials	any	The struct of the trial.	{"key": "value"}
AccessDeniedDetail	object	The details about the access denial. This parameter is returned only if RAM permission verification failed.
	string	The details about the access denial.	{ "AuthPrincipalType": "sub", "PolicyType": "AccountLevelIdentityBasedPolicy", "NoPermissionType": "NoPermission" }

Examples

Sample success responses

JSONformat

{
  "RequestId": "3F190916-B3E5-5D1E-AD0C-35C0DF105F51",
  "Code": "INVALID_USER_OR_EXP",
  "Message": "Missing 'user_id' in request.",
  "TotalCount": 5,
  "Trials": [
    {
      "key": "value"
    }
  ],
  "AccessDeniedDetail": {
    "key": {
      "AuthPrincipalType": "sub",
      "PolicyType": "AccountLevelIdentityBasedPolicy",
      "NoPermissionType": "NoPermission"
    }
  }
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2024-10-21	The response structure of the API has changed	View Change Details
2024-07-26	The internal configuration of the API is changed, but the call is not affected	View Change Details