Soft-delete one of the caller's client accounts.

DELETE

/partner/accounts/{client_account_id}

const url = 'https://api.siteqwality.com/partner/accounts/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';
const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://api.siteqwality.com/partner/accounts/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>'

Marks the client account deleted and nothing else. That single flag is what every downstream consequence keys on, and each one is what removing a client should mean:

the client’s own users lose access,
the client’s checks stop running,
the client can no longer be opened with X-SQ-Account, and
the client slot is freed immediately, so you can add a replacement.

The client’s data is retained per the retention policy. This is not an erasure endpoint. Suspension history is left intact.

Authorizations

bearer_auth

Parameters

Path Parameters

client_account_id

required

string format: uuid

Client account identifier

Responses

200

Client account removed

401

Missing or invalid authentication

403

Caller is not an admin, or the account is not in the partner program

404

No live client account of yours with that id

500

Internal server error