GetCopilotHistory - Alibaba Cloud Linux - 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

sysom:GetCopilotHistory

list

*All Resource

*

None

Request syntax

POST /api/v1/copilot/get_copilot_history HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The request body.
count	integer	Yes	The number of historical chat records to request, generally fewer than 100.	100

Response elements

Element	Type	Description	Example
	object	Schema of Response
code	string	The error code.	SysomOpenAPI.InvalidParameter
data	array<object>	The list of chat records. The length equals the requested number. If the actual chat records are fewer than the requested number, the actual number is returned. Format: [{"user":"","content":"".question,"time":""},{...}]
	object	The response data.
content	string	The chat content text.	The specific content replied by Copilot
time	string	The chat record time, of the string type.	2024-09-02 10:02:39
user	string	The role identifier. Valid values: user: the user. copilot: the bot.	user copilot
message	string	The error message. If `code == Success`, this field is empty. Otherwise, this field contains the request error message.	SysomOpenAPIAssumeRoleException: EntityNotExist.Role The role not exists: acs:ram::xxxxx:role/aliyunserviceroleforsysom
requestId	string	Id of the request	2D693121-C925-5154-8DF6-C09A8B369822

Examples

Success response

JSON format

{
  "code": "SysomOpenAPI.InvalidParameter",
  "data": [
    {
      "content": "Specific content replied by Copilot",
      "time": "2024-09-02 10:02:39",
      "user": "user\ncopilot"
    }
  ],
  "message": "SysomOpenAPIAssumeRoleException: EntityNotExist.Role The role not exists: acs:ram::xxxxx:role/aliyunserviceroleforsysom",
  "requestId": "2D693121-C925-5154-8DF6-C09A8B369822\n"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.