Skip to main content
POST
Create a workspace

Authorizations

Authorization
string
header
required

Enter your API key with the Bearer prefix — e.g. Bearer sk_live_xxx (production) or Bearer sk_test_xxx (sandbox)

Body

application/json
name
string
required

Workspace display name.

Required string length: 1 - 100
Example:

"Support Bot"

integrations
enum<string>[]

Toolkit slugs to expose (e.g. github, gmail). Omit or pass [] to expose all integrations.

Available options:
github,
gmail,
hubspot,
jira,
monday-crm,
notion,
pipedrive,
quickbooks-online,
salesforce,
slack,
xero,
zoho-books,
zoho-crm
Example:
openRouterApiKey
string
write-only

Optional per-workspace OpenRouter API key (bring-your-own LLM key). Input-only: it is validated, encrypted at rest, and NEVER returned in any response. Setting it routes this workspace's chat through OpenRouter; when omitted, the platform default model is used. Use DELETE /mcp/workspaces/{id}/llm-key to remove it later.

Minimum string length: 8
Example:

"sk-or-v1-xxxxxxxxxxxxxxxxxxxxxxxx"

model
string

Optional OpenRouter model id in vendor/model format. Only meaningful alongside (or after) an openRouterApiKey.

Example:

"anthropic/claude-sonnet-4-6"

statelessMode
boolean
default:false

When true, POST /mcp/{workspaceId}/chat for this workspace persists NOTHING (no session, messages, tool I/O, or end-user context) and the caller must supply prior turns via the history field on each chat request. Usage metadata (token/request counts) is still recorded for billing; analytics events are content-free. Default false.

Example:

false

Response

Workspace created.

data
object
required