Get plugin release details¶
Read the selected plugin release’s metadata, connection requirements, and capability definitions.
GET https://api.moi.matrixorigin.cn/v5/workspaces/{workspace_id}/plugin-releases/{release_id}
Before you call this API¶
Prepare the target Workspace ID and a personal access token that can access the resources and perform this operation. Use actual resource identifiers for workspace_id and release_id in the path. Also supply the Workspace ID in X-Workspace-ID. See Shared objects and inputs for environment variable sources.
Query parameters¶
curl -X GET "https://api.moi.matrixorigin.cn/v5/workspaces/$WORKSPACE_ID/plugin-releases/$RELEASE_ID" \
-H "X-API-Key: $AI_STUDIO_API_KEY" \
-H "X-Workspace-ID: $WORKSPACE_ID" \
--get \
--data-urlencode "namespace=$RELEASE_NAMESPACE"
First set $RELEASE_ID to an ID from the release list. Read requirement keys, profiles, drivers, and resource configuration in connections.requirements. Use these values to create a connection; do not supply a custom service endpoint.
Field |
Type |
Required |
Description |
|---|---|---|---|
|
string |
Yes |
system or workspace; no default. |
Successful response¶
{
"code": 0,
"data": {
"publication": {
"id": "pr_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"workspace_id": "workspace_example",
"registry": "workspace",
"publisher": "publisher_example",
"name": "example",
"version": "1.0.0",
"digest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"description": "示例插件",
"published_by": "user_example",
"created_at": "2026-11-11T00:00:00Z"
},
"manifest": {
"$schema": "",
"name": "example",
"version": "1.0.0",
"description": "示例插件"
},
"connections": {
"requirements": {},
"components": {}
},
"profile_digests": {},
"servers": {},
"operations": {},
"skills": []
}
}
Field |
Type |
Description |
|---|---|---|
|
integer |
0 on success. |
|
object |
Data returned by this operation. |
|
object |
Release metadata. |
|
object |
Resource fields; see Shared objects and states. |
|
object |
Connection requirements and configuration defined by the release. |
|
object |
Digest mapping for requirements and profiles. |
|
object |
Resource fields; see Shared objects and states. |
|
object |
Resource fields; see Shared objects and states. |
|
array |
Resource fields; see Shared objects and states. |
Error responses¶
Handle numeric business-error code, message, and details.reason separately from authorization-layer string codes. See Errors and states. On a state or version conflict, read the current resource first; do not automatically change identifiers or retry writes.