Occurs when a subdomain clone request has been completed.

📘
Note:
This is only applicable to approved Partners who have access to subdomain provisioning via the API. The webhook must be configure within the main partner bundle subdomain.

The status will reflect as succeeded or failed. If failed, additional notes will be provided within the status attribute.

Example payload:

{
  "event_key": "account.provisioned",
  "occurred_at": "2026-06-22T10:30:35.764-06:00",
  "data": {
    "subdomain": "subdomainABC",
    "status": "succeeded"
  }
}

Account Provisioning Failure Reference

Errors returned during account creation and template cloning are provided with guidance on whether the provisioning operation can be safely retried.

{
  "event_key": "account.provisioned",
  "occurred_at": "2026-06-22T10:30:35.764-06:00",
  "data": {
    "subdomain": "subdomainABC",
    "status": "failed:<reason>"
  }
}

Error Messages

Failed Reason Message	Description	Retryable	Reason
`subdomain already taken`	The requested subdomain is already in use by another account.	❌ No	This is a permanent conflict. Retrying will fail with the same error. The requester must choose a different subdomain.
`Account save failed`	The destination account record could not be persisted to the database.	✅ Yes	Transient database connectivity or constraint violations may resolve by retrying the provisioning process.
`Tenant creation failed`	The multi-tenant database schema could not be created for the new account.	✅ Yes	Transient database or resource allocation issues may resolve by retrying the provisioning process.
`Tenant tables clone failed`	State cloning from the template account's tenant tables did not complete successfully.	✅ Yes	Transient errors during data replication (locks, timeouts) may resolve by retrying the provisioning process.
`Document assets clone failed`	Document assets could not be cloned from the template account (e.g., S3 upload/download failure).	❌ No	This is a permanent conflict. Retrying will fail with `subdomain already taken`error. The requester must choose a different subdomain.
`Settings clone failed`	Account settings/configuration could not be cloned from the template account.	✅ Yes	Transient database or state consistency issues may resolve by retrying the provisioning process.
`Feature flags clone failed`	Feature flags could not be cloned from the template account.	✅ Yes	Transient database access issues may resolve by retrying the provisioning process.

Handling Retries

Non-retryable (subdomain already taken, Document assets clone failed) — Request a different subdomain. Do not queue a retry.
Retryable — the failure is transient. Retry the operation; if it fails repeatedly, escalate rather than continuing to retry.