Skip to main content
DELETE /api/v2/accounts/{customerId} Hard-deletes an account under your organization. Only CHILD-type accounts can be deleted, and the caller must be an ADMIN on the organization (or a Scope3 SuperAdmin). The request is refused if the account still has linked resources. For normal account deletion, send no request body and remove dependent resources first.

​
Request

curl

​
Parameters

​
Staging canary cleanup proof

runOwnedCleanupReceipt is reserved for the automated Scope3 publisher-onboarding staging canary. It is not a general cascade-delete option, and customer integrations must omit it.
After the internal preparation endpoint has persisted an exact cleanup receipt, the canary reconciler attaches that receipt when finalizing its disposable test seller:
The service accepts this receipt only for a marked disposable publisher-onboarding test child, from a Scope3 SuperAdmin acceptance-test request scoped to its exact parent. It rechecks the persisted account, campaign, strategy, and advertiser proof before deletion. Missing cleanup steps, new dependencies, or any receipt mismatch fail closed.

​
Response

204 No Content — the account was deleted. The response body is empty.

​
Errors

  • 400 VALIDATION_ERROR — the account is not a deletable child, or the optional canary receipt is malformed.
  • 401 UNAUTHORIZED — missing or invalid bearer token.
  • 403 FORBIDDEN — caller is not an ADMIN on the target account’s parent organization (including when an existing account is outside the caller’s organization), or receipt-bound cleanup was requested without the required internal authority.
  • 404 NOT_FOUND — the account does not exist.
  • 409 CONFLICT — the account still has linked resources, or the receipt no longer exactly matches the target child and its cleanup state.
See Errors for the full error contract.

Account tasks

All account operations

Create account

Add an account under your organization

List accounts

Accounts you can access