Rename workspace
Rename the operator's workspace once the real business name surfaces in the interview. Workspaces are named whatever the user typed at signup, often a placeholder like 'My Workspace'. Call this exactly once during onboarding, mid-interview, when you have a confident name. Changes the display name only, the slug stays stable, so existing agent handles and links keep working.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/set_workspace_name" \ -H "Content-Type: application/json" \ -d '{ "name": "string", "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Set integration OpenAPI spec POST
Set the OpenAPI 3.x spec that defines a custom HTTP integration's callable actions (the paths/operations an agent's tools can call). Pass the integration id (from list_workspace_integrations) and the spec as a JSON object. The spec is validated (must be OpenAPI 3.x with 'info' + 'paths') before it's stored; an invalid spec is rejected with the specific errors. No credentials go here; API keys and OAuth secrets are set separately via create_workspace_integration and Settings → Connections. Requires workspace-admin.
Set workspace notifications POST
Turn the workspace's observability + simulation notifications on or off and set the recipient email list they all deliver to. Toggles: cronFailure, cronSuccess, resultsCompletion, evalDeferred, dailyReport, weeklyReport, noCallsAlert, frequentCalls, spendCap, agentPublished, transferSpike, agentPerformance, burstUsed, capacityRequestDecided, campaignReply (someone replied to a campaign SMS; on by default, one email per reply), webhookDeliveryFailed (a webhook dropped events after its final retry; on by default, at most one email an hour per webhook). `recipients` REPLACES the list (an empty array clears it, which falls back to the workspace owner). Every field is optional, pass only what you want to change. These are workspace-level, not per-agent. For per-alert delivery of a specific metric alert (email / Slack / webhook), use create_alert or update_alert.