Delete a client workspace
Delete one of your clients' workspaces.
Deletes one of your workspaces. It stops appearing in List your client workspaces and no longer resolves by partner_workspace_id, on every route. Its partner_workspace_id stays yours: you cannot reuse it. You can restore the workspace later. Sending the same request again answers 404.
Route
DELETE/api/v3/partner/workspaces/{partner_workspace_id}
Path parameters
| Parameter | Type | Description |
|---|---|---|
| partner_workspace_id | string | Your own ID for the client workspace, as you chose it at creation. URL-encode it in the path. |
Example request
curl -X DELETE "https://api.getsillage.com/api/v3/partner/workspaces/crm-4821" \
-H "Authorization: Bearer $SILLAGE_MASTER_KEY"Success response
Status: 200 OK
{
"data": {
"partner_workspace_id": "crm-4821",
"deleted": true
}
}Response fields
| Field | Type | Description |
|---|---|---|
| data.partner_workspace_id | string | Your own ID for the workspace that was deleted. |
| data.deleted | boolean | Always true. |
Errors
| Status | Meaning |
|---|---|
| 401 | The master key is missing or invalid. |
| 404 | No workspace found for this partner_workspace_id, including one that is already deleted. |
| 422 | A query parameter is sent: this route takes none, and errors names the parameter. |
| 429 | Rate limit exceeded. |
| 500 | An unexpected server error occurred. |
Error responses use RFC 9457 problem documents with Content-Type: application/problem+json. type is always about:blank; code tells one problem from another, detail says what went wrong this time, and errors names the field at fault.