Restore a deleted client workspace

Brings back a deleted workspace of yours, with its data. Restoring a workspace that is not deleted changes nothing and answers 200. The route takes no body.

A workspace is refused when you now have another live workspace on the same domain: delete that one first, or create a persona in it instead.

Route

POST/api/v3/partner/workspaces/{partner_workspace_id}/restore

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 POST "https://api.getsillage.com/api/v3/partner/workspaces/crm-4821/restore" \
  -H "Authorization: Bearer $SILLAGE_MASTER_KEY"

Success response

Status: 200 OK

{
  "data": {
    "partner_workspace_id": "crm-4821",
    "name": "Acme",
    "domain": "acme.com",
    "archived": false,
    "created_at": "2026-10-16T09:00:00.000Z"
  }
}

Errors

Status	Meaning
401	The master key is missing or invalid.
404	No workspace found for this `partner_workspace_id`.
409	You already have another live workspace on this domain (`You already have a workspace for acme.com (crm-9000). Create a persona in it instead: each persona has its own lists, signal setups and leads.`), or the workspace was permanently erased (`This workspace was permanently erased and cannot be restored.`), or another create or restore is running for you at the same moment (`A workspace is being created or restored for you right now. Retry in a moment.`).
422	A body field is sent (`Unknown field: <field>`): this route takes no body. A query parameter is refused too.
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.