v2DeprecatedWorkspaces
Create a workspace
Provision a new Sillage workspace for an end customer.
Provisions a new Sillage workspace for an end customer. The partner_workspace_id must be unique per partner — it is your stable reference for all subsequent operations on this workspace.
Create a workspace
POST/api/v2/partner/workspaces
Request body
| Field | Type | Required | Description |
|---|---|---|---|
| partner_workspace_id | string | Yes | Your stable identifier for this workspace. Used in all subsequent requests. Must be unique. |
| end_customer_email | string | Yes | Email address of the end customer who owns this workspace. |
| name | string | Yes | Display name for the workspace. |
| domain | string | No | Primary domain of the end customer (e.g. acme.com). No protocol, path, or spaces. |
| signal_batch_frequency_hours | integer | No | How often, in hours, detected signals are batched. Must be a positive integer. Defaults to 2. |
Example request
curl -X POST "https://api.getsillage.com/api/v2/partner/workspaces" \
-H "Authorization: Bearer $SILLAGE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"partner_workspace_id": "ws_123",
"end_customer_email": "alice@acme.com",
"name": "Acme Workspace",
"domain": "acme.com",
"signal_batch_frequency_hours": 2
}'Example response
Status: 201 Created
{
"data": {
"id": 101,
"name": "Acme Workspace",
"domain": "acme.com",
"is_archived": false,
"partner_workspace_id": "ws_123"
}
}Response fields
| Field | Type | Description |
|---|---|---|
| id | integer | Identifier for the workspace. |
| name | string | Display name of the workspace. |
| domain | string or null | Primary domain of the end customer, or null if not set. |
| is_archived | boolean | Whether this workspace has been archived. |
| partner_workspace_id | string | Your partner-side identifier, echoed back where applicable. |
Errors
| Status | Meaning |
|---|---|
| 401 | The master key is missing or invalid. |
| 403 | The master key is not authorized to access this resource. |
| 422 | Invalid request body. |
| 429 | Too many requests. |
| 500 | An unexpected server error occurred. |
Error responses use RFC 9457 problem documents with Content-Type: application/problem+json.