Skip to main content
A personal API key lets you reach your workspace’s models from outside Langdock, so you can use them in coding tools like Claude Code or Codex, or in a project of your own. The key authenticates as you, which means it spends your usage budget and reaches the completion endpoints only.
API keys section in account settings showing the extra usage budget and when it resets
Your admin has to give you access before API keys appears in your account settings, and you need usage budget to spend. On Langdock Cloud that means extra usage is enabled and your effective extra usage limit is above zero. On BYOK and dedicated deployments it means your admin set an individual extra usage limit above zero, where plan and group limits don’t apply to personal keys and extra usage doesn’t have to be enabled. Whatever you spend through the key comes out of the same budget as your chat and agent usage. On trial workspaces you can only create a key once API keys have been enabled for the trial.

​
Create a personal API key

1

Open API keys

Go to Settings > Account > API keys.
2

Enter the key details

Your API keys section with the Create API key button
Click Create API key. Give the key a name that tells you where it’s used, so you know which tool to update later, and choose when it expires.
3

Create and copy the key

Create a new API key dialog with fields for name and expiry and a summary of what the key can do
Click Create API key, then copy the key and store it somewhere safe. Langdock shows it once and never again.
Never share a personal API key. It authenticates as you and spends your budget, so anyone who has it is working as you. Use a workspace API key for shared applications and automations, and see API key best practices for storing keys safely.
The page also tracks how much of your budget you have used and when it resets. If there is nothing left to spend, you can request a higher limit right there when usage requests are enabled, or ask your workspace admin.

​
Connect a tool

Connect your tools walks you through the setup for Claude Code, Claude Desktop, OpenCode, Codex, and direct API calls with cURL. Pick an available model and the examples update to match, then follow the steps for your tool. Your key works with the OpenAI compatible Chat Completions and Responses APIs, the Anthropic Messages API, the Google Completion API, and the Mistral Completion API. Which of them you can call depends on the models configured for your workspace. Available models shows what you can pick for the built-in OpenAI and Anthropic guides, and for Google and Mistral you follow the API documentation instead. Personal keys stop at the completion endpoints. The Agent, Embedding, Knowledge Folder, Integrations, Skills, Usage Export, and Audit Logs APIs need a workspace API key with the matching scope.

​
Rotate or revoke a key

Open the menu next to a key under Your API keys:
  • Rotate key replaces the secret. The old one stops working immediately, so update every connected tool with the new key.
  • Revoke key switches the key off for good.
Your workspace admin can revoke your keys as well. They also stop working if your admin takes away your access to personal API keys or deactivates your workspace membership.