Agent Publish API

​

Before You Start

• Legacy Assistants API: This is the new Agents API with native Vercel AI SDK compatibility. If you’re using the legacy Assistants API, see the migration guide.

​

Base URL

https://api.langdock.com/agent/v1/publish

​

Draft vs. Published Version

​

Use Cases

• Promote draft edits made via the Update API into a new active version
• Roll out changes programmatically as part of a CI/CD pipeline
• Release a new revision with an optional change description shown in version history

​

Parameters

​

Example

const axios = require("axios");

async function publishAgent(agentId, description) {
  const response = await axios.post(
    "https://api.langdock.com/agent/v1/publish",
    {
      agentId: agentId,
      description: description,
    },
    {
      headers: {
        Authorization: "Bearer YOUR_API_KEY",
        "Content-Type": "application/json",
      },
    },
  );

  console.log("Published version:", response.data.version);
}

publishAgent(
  "550e8400-e29b-41d4-a716-446655440000",
  "Tightened the system prompt",
);

​

Response Format

​

Success Response (200 OK)

{
  status: "success";
  message: "Agent published successfully";
  version: {
    id: string;          // UUID of the new version
    version: number;     // Monotonically increasing version number
    createdAt: string;   // ISO 8601 timestamp
  };
}

​

Validation Rules

• Agent access — A personal key can publish when its owner can edit the agent, including through a group or the workspace, or when the key has an editor or owner grant. A workspace key needs an editor or owner grant on the key.
• Workspace match — The agent must belong to the same workspace as the API key.
• Agents only — Projects (type=PROJECT) are not supported and will return 403.
• Has draft changes — The draft must differ from the latest published version. Publishing with no pending changes returns 409 Conflict, mirroring the disabled “Update” button in the UI.

​

Error Handling