Skip to main content
Using our API via a dedicated deployment? Just replace api.langdock.com with your deployment’s base URL: <deployment-url>/api/public
The Skills API lets you manage Skills programmatically. Use it to sync Skills from a repository, create reusable instruction sets, attach accessible integrations, and import SKILL.md files or zip archives.

​
API Key Scope

All Skills API endpoints require an API key with the SKILL_API scope.
Create an API key with SKILL_API scope in your workspace settings. The API acts as the user who created the key, including their Skills product access and Skill permissions.

​
Available Endpoints

MethodEndpointDescription
GET/skills/v1List Skills
POST/skills/v1Create a Skill
GET/skills/v1/{skillId}Get a Skill
PATCH/skills/v1/{skillId}Update a Skill
DELETE/skills/v1/{skillId}Delete a Skill
POST/skills/v1/importImport a Skill

​
Skill Object

Skills API responses use the same Skill object across endpoints: 
{
  id: string;
  name: string;
  slug: string;
  description: string;
  instructions: string;
  integrationIds: string[];
  createdAt: string;
  updatedAt: string;
}

​
Supported Skill Types

The API only manages Skills that users create in the workspace. System Skills, templates, and Skill Packs are not returned or modified through these endpoints. For item endpoints, use the Skill id. The slug field is supported as a list filter and as the upsert key for imports, but reads, updates, and deletes use skillId.

​
Permissions

Requests use the user who created the API key for permissions and access:
ActionRequired access
List or get SkillsViewer access to the Skill
Create Skills or create through importcreateSkills workspace permission
Update Skills or upsert through importEditor access to the Skill
Delete SkillsOwner access to the Skill, or admin access
If you attach integrations with integrationIds, each integration must be enabled in your workspace.

​
Rate Limits

The Skills API follows standard API rate limits. If you exceed the limit, you’ll receive a 429 response. Wait and retry with exponential backoff.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.