API Keys
Create API Key
Generate a new API key scoped to specific instances and permissions.
POST
Create an API key that grants access to one or more instances within your organization. Every key is scoped with explicit permissions so you can hand out only the access that’s actually needed.Documentation Index
Fetch the complete documentation index at: https://docs.chowder.dev/llms.txt
Use this file to discover all available pages before exploring further.
Authorization
Requires an organization-level API key in theAuthorization header.
Request Body
A human-readable name for the key. Pick something descriptive — you’ll thank yourself later when you’re staring at a list of keys.
Array of instance IDs this key should have access to.
Array of permission scopes to grant. Valid values:
| Permission | What it unlocks |
|---|---|
read | View instance details and status |
interact | Send messages to the instance |
configure | Modify instance settings and install skills |
files | Read and write files in the instance workspace |
channels | Manage channels (create, update, delete) |
Optional ISO 8601 datetime string. If set, the key automatically becomes inactive after this time. If omitted, the key lives until you revoke it.
Response
Unique identifier for the key.
The organization this key belongs to.
The name you gave the key.
Always
chd_sk_. Useful for identifying Chowder keys in your configs.Whether the key is currently active.
Expiration datetime, if one was set.
When the key was created.
The full API key, prefixed with
chd_sk_. This is the value you’ll use in Authorization headers.