Erase organization data

Erases One-owned organization records and verifies remaining local KV entries; excludes Auth credentials and the global catalog.

Outcome

Erases One-owned organization records and verifies remaining local KV entries; excludes Auth credentials and the global catalog.

Before you start

Verify the intended environment, authenticated identity and explicitly authorized ownership context.
Discover the published settings:write permission and any required resource grant.
Approve the actual effects before confirming the unchanged planned request. Fixture identifiers, recipients and provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_one.organizations.data.erase --detail --json

organizationId: Exact active authorized organization id. Organization erasure/export covers One’s records in that whole organization.

Request

DELETE /api/organizations/{organizationId}/data

Inspect and test this action.

Input fields

Field	Required	Meaning	Constraints
`organizationId`	Required	Exact active authorized organization id. Organization erasure/export covers One’s records in that whole organization.	{"type":"string","minLength":1}

Inspect nested fields.

Interpret the response

Read data.erased, verificationPending and remainingKv, then export the same organization and inspect each collection. Active billing can refuse erasure.

Inspect the declared output schema and captured variants.

Worked examples

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.

Save the reviewed input below as payload.json; substitute discovered identifiers and bind credential/resource context separately. CLI:

topolo actions validate app_topolo_one.organizations.data.erase --data @payload.json --json
topolo actions plan app_topolo_one.organizations.data.erase --data @payload.json --json
topolo actions call app_topolo_one.organizations.data.erase --data @payload.json --confirm --detail --json

MCP planning and execution use the same reviewed input:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_one.organizations.data.erase",
    "input": {
      "organizationId": "org_int_1"
    }
  }
}

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_one.organizations.data.erase",
    "input": {
      "organizationId": "org_int_1"
    },
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "organizationId": "org_int_1"
}

Captured response:

{
  "data": {
    "organizationId": "org_int_1",
    "erased": true,
    "eraseRequested": true,
    "verificationPending": false,
    "remainingKv": 0,
    "counts": {
      "dashboardLayouts": 1,
      "launches": 0,
      "pushSubscriptions": 0,
      "queuedMessages": 0,
      "billingSubscriptions": 0,
      "manualSeatDeliveries": 0,
      "billingAccounts": 0,
      "kv": 1
    },
    "authenticationCredentialsErased": false,
    "globalCatalogErased": false
  }
}

Read data.erased, verificationPending and remainingKv, then export the same organization and inspect each collection. Active billing can refuse erasure.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "organizationId": "org_int_1"
}

Captured response:

{
  "error": "Token validation failed"
}

Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

Verify the result

Read data.erased, verificationPending and remainingKv, then export the same organization and inspect each collection. Active billing can refuse erasure.

Errors and recovery

auth_error (HTTP 401): Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

These are observed local refusals; inspect the raw error body because one SDK code can represent several handler messages. Preserve the request id when available.

Recovery boundary

Retain an approved export before erasure. Inspect partial-erasure diagnostics and re-export before retrying; no published automatic restore exists.

Export organization data: Export TopoloOne-owned launch, push, billing, cache, and workspace-mirror data for the authenticated organization with credential fields redacted.