List team conversations¶
List conversation metadata for a team.
GET https://api.moi.matrixorigin.cn/v5/workspaces/{workspace_id}/agent-teams/{team_id}/sessions
Before you call this API¶
Set BASE_URL to the product API prefix https://api.moi.matrixorigin.cn/v5. For private deployments, use the corresponding product API URL.
Prepare product identity and object identifiers in the same environment.
Request¶
curl --request GET \
"$BASE_URL/workspaces/$WORKSPACE_ID/agent-teams/$TEAM_ID/sessions?limit=50&offset=0" \
--header "X-API-Key: $MOI_KEY" \
--header "X-Workspace-ID: $WORKSPACE_ID"
Next-page example:
curl --request GET \
"$BASE_URL/workspaces/$WORKSPACE_ID/agent-teams/$TEAM_ID/sessions?limit=50&offset=50" \
--header "X-API-Key: $MOI_KEY" \
--header "X-Workspace-ID: $WORKSPACE_ID"
Parameter |
Location |
Type |
Required |
Description |
|---|---|---|---|---|
|
Path |
string |
Yes |
Current Workspace ID, consistent with the product identity and request headers in the same environment. |
|
Path |
string |
Yes |
Team ID from the team list or creation response. |
|
Queries |
integer |
No |
Default 50, maximum 200. Nonpositive or invalid values use 50. |
|
Queries |
integer |
No |
Default 0; negative values use 0. |
In ordinary mode, stop when offset + items.length >= total or items is empty. Concurrent writes may affect offset pagination; total is not a stable snapshot.
The team must be active. Conversations sort by creation time descending, then context_id. Use context_id for subsequent renaming, submission, and message reads.
Successful response¶
{
"code": 0,
"data": {
"items": [
{
"workspace_id": "workspace-example",
"team_id": "team-example",
"context_id": "context-example",
"name": "资料整理",
"created_by_moi_user_id": "user-example",
"updated_by_moi_user_id": "user-example",
"version": 1,
"created_at": "2026-11-12T01:00:00Z",
"updated_at": "2026-11-12T01:00:00Z"
}
],
"total": 1,
"limit": 50,
"offset": 0
}
}
Field |
Type |
Description |
|---|---|---|
|
integer |
0 on success. |
|
object |
HTTP200. Returns the corresponding object; confirm writes with the corresponding read operation.
Error responses¶
Errors and concurrency handling distinguishes parameter, version, member/conversation state, and admission failures.