Use the ListWikiPages operation to list the metadata of currently published Wiki pages in path order.
Prerequisites
-
An AgentStorage instance has been created and its status is
normal, and you have obtained the instance endpoint and instance name. -
An API Key has been created.
-
Wiki operations use the full three-segment Agent Scope (
appId/tenantId/agentId). Each segment must be non-empty, cannot be*, can be up to 128 bytes in length, and cannot contain/. Do not passrunId.
Request parameters
|
Field |
Type |
Required |
Description |
|
|
string |
Yes |
The name of the memory store. |
|
|
object |
Yes |
The full three-segment Agent Scope. The rules are the same as those for |
|
|
int |
No |
The number of entries to return. Default value: 50. Maximum value: 100. |
|
|
string |
No |
The opaque pagination token returned by the previous page. |
Request example
When you use API Key authentication, pass the instance name and API Key through the x-ots-instancename and x-ots-apikey request headers.
curl -X POST https://<endpoint>/ListWikiPages \
-H "x-ots-instancename: <instance-name>" \
-H "x-ots-apikey: <your-api-key>" \
-H "Content-Type: application/json" \
-d '{
"memoryStoreName": "agent_memory",
"scope": {
"appId": "app-001",
"tenantId": "user-001",
"agentId": "assistant"
},
"limit": 20
}'
Response
|
Field |
Description |
|
|
The list of page metadata. For field descriptions, see [Wiki page object](./get-wiki-page.md#wiki-页面对象). The list result does not return |
|
|
The token for the next page. Omitted when there are no more pages. |
Even if a new build is published during pagination, subsequent pages still belong to the same published version that was locked by the first request. Do not modify or parse nextToken.