Create a plugin account connection¶
Create an account connection according to the plugin release requirements. Complete authorization separately.
POST https://api.moi.matrixorigin.cn/v5/workspaces/{workspace_id}/plugin-connections
Before you call this API¶
Prepare the target workspace ID and a personal access token with access to the resource and the required action privileges. Use actual resource identifiers for workspace_id in the path and also set X-Workspace-ID. Examples use jq to construct JSON; install it first. See Common objects and inputs for environment-variable sources.
Request body¶
curl -X POST "https://api.moi.matrixorigin.cn/v5/workspaces/$WORKSPACE_ID/plugin-connections" \
-H "X-API-Key: $AI_STUDIO_API_KEY" \
-H "X-Workspace-ID: $WORKSPACE_ID" \
-H 'Content-Type: application/json' \
--data-binary "$(jq -n --arg RELEASE_NAMESPACE "$RELEASE_NAMESPACE" --arg RELEASE_ID "$RELEASE_ID" --arg CONNECTION_REQUIREMENT "$CONNECTION_REQUIREMENT" --arg CONNECTION_PROFILE "$CONNECTION_PROFILE" '
{
"release_namespace": $RELEASE_NAMESPACE,
"release_id": $RELEASE_ID,
"requirement": $CONNECTION_REQUIREMENT,
"profile": $CONNECTION_PROFILE,
"name": "我的插件账号"
}
')"
The example uses oauth configuration. Creation saves only the connection and does not authorize the account. managed_session may select an executor supported by the deployment. The server resolves the managed alias to an actual executor. Use the actual value read from the connection for subsequent installation bindings.
Fields |
Type |
Required |
Description |
|---|---|---|---|
|
string |
Yes |
system or workspace. |
|
string |
Yes |
Selected release ID from the release list. |
|
string |
Yes |
Requirement key in the release connections.requirements. |
|
string |
Yes |
Configuration key in profiles for that requirement. |
|
string |
Yes |
Caller-supplied account description. The service generates the returned name and saves this value in description. |
|
string |
Conditional |
Executor identifier required by managed_session profiles; omit or leave empty for other drivers. |
JSON objects reject unknown fields, duplicate keys, and multiple consecutive objects. Total request body size must not exceed 1 MiB.
Successful response¶
{
"code": 0,
"data": {
"id": "connection_example",
"workspace_id": "workspace_example",
"name": "provider · connection_example",
"description": "我的插件账号",
"status": "active",
"kind": "plugin",
"endpoint_uri": "https://service.example.invalid",
"auth_type": "oauth2",
"visibility": "private",
"version": 1,
"created_at": "2026-11-11T00:00:00Z",
"updated_at": "2026-11-11T00:00:00Z"
}
}
Field |
Type |
Description |
|---|---|---|
|
integer |
0 on success. |
|
object |
Data returned by this operation. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Current state; interpret using this page’s conditions and common objects. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
|
integer |
Current resource version; used as expected_version for writes. |
|
string |
Resource fields; see Shared objects and states. |
|
string |
Resource fields; see Shared objects and states. |
Error response¶
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.