# Get plugin release details

```{raw} html
<div class="mo-api-page-show-toc" aria-hidden="true"></div>
```

Read the selected plugin release's metadata, connection requirements, and capability definitions.

```text
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](objects.md#input-identifiers) for environment variable sources.

## Query parameters

:::::::{div} mo-api-tabs
::::::{tab-set}
:::::{tab-item} Request example

```bash
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"
```

:::::
:::::{tab-item} Parameters

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 |
| --- | --- | --- | --- |
| `namespace` | string | Yes | system or workspace; no default. |

:::::
::::::
:::::::

## Successful response

:::::::{div} mo-api-tabs mo-api-response-tabs
::::::{tab-set}
:::::{tab-item} Response example

```json
{
  "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": []
  }
}
```

:::::
:::::{tab-item} Fields

| Field | Type | Description |
| --- | --- | --- |
| `code` | integer | 0 on success. |
| `data` | object | Data returned by this operation. |
| `data.publication` | object | Release metadata. |
| `data.manifest` | object | Resource fields; see [Shared objects and states](objects.md). |
| `data.connections` | object | Connection requirements and configuration defined by the release. |
| `data.profile_digests` | object | Digest mapping for requirements and profiles. |
| `data.servers` | object | Resource fields; see [Shared objects and states](objects.md). |
| `data.operations` | object | Resource fields; see [Shared objects and states](objects.md). |
| `data.skills` | array | Resource fields; see [Shared objects and states](objects.md). |

:::::
::::::
:::::::

## Error responses

Handle numeric business-error `code`, `message`, and `details.reason` separately from authorization-layer string codes. See [Errors and states](objects.md#error-responses). On a state or version conflict, read the current resource first; do not automatically change identifiers or retry writes.
