Claude Platform Docs

Plugin-Version erstellen

$ ant beta:organization:plugins:versions create
POST/v1/organizations/plugins/{plugin_id}/versions

Fügt einem organisationseigenen Plugin eine Version hinzu, indem die Dateien der neuen Version hochgeladen werden; sie wird zur an Mitglieder ausgelieferten Version, sofern die ausgelieferte Version des Plugins nicht fixiert wurde.

Der Upload ist dasselbe multipart/form-data wie beim Erstellen eines Plugins: die Dateien der Version (files, jeder Teil gesendet als files[]) und optional release_notes. Der name des hochgeladenen Manifests muss dem name des Plugins entsprechen. Gibt die gespeicherte Version zurück; lies das Plugin erneut aus, um zu sehen, welche Version es ausliefert.

Nur ein Plugin in einem manual-Marketplace nimmt Uploads an; ein Plugin, das aus einem Repository synchronisiert wird, erhält seine Versionen aus dem Repository. Wenn sich das Plugin im Library-Marketplace der Organisation befindet, wird eine Version, die einen Skill mit dem Namen eines Organisations-Skills (eines Skills, den ein Administrator für die gesamte Organisation in claude.ai hochgeladen hat) hinzufügt, mit 409 abgelehnt: error_code skill_name_taken, mit diesem Namen in details.skill_name. Ein 503 mit error_code registration_pending bedeutet, dass die Version gespeichert wurde, aber noch nicht nutzbar ist; ein späteres Erstellen einer Version für das Plugin schließt sie ab.

Ein ausgearbeitetes Beispiel findest du unter Eine Version erstellen im Leitfaden zur Plugins API.

Akzeptierte Anmeldedaten: ein Admin-API-Key mit dem Scope write:plugins.

Jede Anfrage muss den Beta-Header anthropic-beta: ce-plugins-2026-09-01 enthalten. Eine Anfrage ohne ihn gibt 404 zurück, genau so, als ob der Endpunkt nicht existieren würde. Die Plugins API befindet sich in der Beta und ist nur für Claude Enterprise-Organisationen verfügbar. Sie ist nicht für Claude Platform (Claude Console)-Organisationen oder für Organisationen mit aktivierter HIPAA-Readiness verfügbar.

Parameters
--plugin-id: string⁠Path parameter

ID of the Plugin (prefixed plugin_).

--file: array of string

The version's files: one part per file, the part's filename being the file's path within the Plugin (for example skills/review-pr/SKILL.md), or a single .zip or .plugin archive holding them all. On the wire each part is named files[], and a part named plain files is not read; with cURL, -F 'files[]=@SKILL.md;filename=skills/review-pr/SKILL.md'. The files must include the manifest, .claude-plugin/plugin.json.

--release-notes: optional string

Release notes stored with the version and shown in its version history in claude.ai; up to 5,000 characters.

maxLength5000
--beta: optional array of AnthropicBeta⁠Header parameter

This endpoint is in beta: requests must send ce-plugins-2026-09-01 in this header.

Returns
beta_plugin_version: object{ type: "plugin_version", id, components, 9 more }
type: "plugin_version"

Always plugin_version.

id: string

The version's ID.

components: array of BetaPluginComponent { type, description, name }

What the version contains; null when not enumerated.

type: "agent" or "cli" or "command" or 3 more

The kind of component.

One of the following:
"agent"
"cli"
"command"
"hook"
"mcp_server"
"skill"
description: string

What the component declares about itself; always null for MCP servers, hooks, and CLIs.

name: string

The component's name: a skill's, command's or agent's name, an MCP server's key in the manifest, the event a hook runs on, or a CLI's executable.

content_scan: object{ assessment, reason, status }

This version's content scan; null when it has not been scanned.

assessment: "fail" or "pass" or "unknown" or "warn"

The scan's verdict; set only when status is completed.

One of the following:
"fail"
"pass"
"unknown"
"warn"
reason: string

The primary mechanism behind a warn or fail, such as credential-exposure or guardrail-tampering; a mechanism this API does not yet name reads as other. Null on a pass, whenever assessment is null, and when no mechanism is reported for the verdict.

status: "completed" or "errored" or "processing"

processing while a scan runs, completed when it ran to completion, errored when it could not run or its outcome cannot be read.

One of the following:
"completed"
"errored"
"processing"
created_at: string

RFC 3339.

formatdate-time
created_by: BetaPluginUserActor or BetaPluginAPIActor

Who uploaded this version; null when not recorded.

One of the following:
beta_plugin_user_actor: object{ type: "user_actor", email_address, user_id }
type: "user_actor"

A member of the organization.

email_address: string

The member's email address; may be null, for example when they are no longer a member of the organization.

user_id: string

The member's User ID.

beta_plugin_api_actor: object{ type: "api_actor", api_key_id }
type: "api_actor"

An Admin API key, in the same form the Compliance API activity feed uses for it.

api_key_id: string

The key's ID.

description: string

The manifest's description; null when it declares none.

display_name: string

The manifest's display name; null when it declares none.

manifest_version: string

The manifest's version, normalized for display: one leading v or V is dropped, and the result is returned only if it is 1 to 64 characters, starts with a digit, and uses only ASCII letters, digits, ., +, and -; otherwise null. For example, "v1.4.0" is returned as "1.4.0", and "latest" as null. For a synchronized plugin, the version of its marketplace.json entry can take the place of the manifest's version. It is also null for a version stored before claude.ai began recording this field (August 2026).

plugin_id: string

The Plugin's ID.

reach: "contained" or "privileged" or "remote"

How far the version reaches: remote, privileged, contained, or null, as defined on the Plugin's reach.

One of the following:
"contained"
"privileged"
"remote"
release_notes: string

As supplied with the upload; null when none were supplied.

Plugin-Version erstellen
ant beta:organization:plugins:versions create \
  --api-key my-anthropic-api-key \
  --plugin-id plugin_id \
  --file 'Example data'
Returns Examples
Response 200
{
  "id": "pluginver_01KaZmQpRsTuVwXyZ2b4c6d8",
  "components": [
    {
      "description": "description",
      "name": "review-pr",
      "type": "skill"
    }
  ],
  "content_scan": {
    "assessment": "warn",
    "reason": "credential-exposure",
    "status": "completed"
  },
  "created_at": "2026-03-14T09:26:53.589793Z",
  "created_by": {
    "email_address": "user@example.com",
    "type": "user_actor",
    "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q"
  },
  "description": "Reviews pull requests against your team's conventions.",
  "display_name": "Code Review Helper",
  "manifest_version": "1.2.0",
  "plugin_id": "plugin_01JyHfbRkZvD1gW7oTqXc3Ne",
  "reach": "contained",
  "release_notes": "Adds a review checklist for database migrations.",
  "type": "plugin_version"
}