Creates a new child organization under the caller’s organization. The child org is created in an unapproved state — approval happens separately through the Etherfuse approval workflow.
Optionally include wallets and a bank account to set up the child org in a single call. Wallets are registered but not claimed — claiming and KYC sync happen after org approval.
If any provided UUID collides with an existing record, the request returns 409.
All fields are optional — sending an empty body {} creates a bare organization with no wallets or bank account.
Every organization has an accountType of either personal (an individual customer
completing KYC) or business (a company completing KYB). The two are handled differently
downstream: personal orgs go through individual KYC and Plaid; business orgs go through
KYB and skip per-wallet compliance.
personal — pass userInfo so the end user records are created and we can email them on status changes.business — userInfo is rejected (business orgs do not have a single end user).accountType is currently optional and defaults to personal. It will become required
in a future release — start sending it explicitly now.
Documentation Index
Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt
Use this file to discover all available pages before exploring further.
API key for authentication. Pass the key directly (e.g., Authorization: your-api-key). Do not use a Bearer prefix.
Optional UUID to use as the organization's primary key. If omitted, a UUID is generated automatically.
Optional display name for the new organization. At most 200 characters. If omitted, defaults to "Customer for {parent org name}".
200Type of organization. Defaults to personal. Will become required in a
future release. See "Account types" above for guidance.
personal, business Optional info about the end user (the individual customer behind a personal organization).
Recommended. When provided, Etherfuse pre-creates the user record so that when the customer eventually signs in via the hosted onboarding UI their Firebase identity attaches to the right user. It also enables personalized status-change emails (KYC approved/rejected, bank account verified, etc.).
Will eventually be required for personal organizations. Reject early in your integration if you don't have this data — partners that don't migrate before the cutover will start receiving 400 errors.
{
"email": "[email protected]",
"displayName": "Ana García"
}Optional wallets to register for the new organization. Maximum 50 wallets per request.
50Optional default partner fee in basis points for this child organization (0–500). If omitted, defaults to 0 (no partner fee).
0 <= x <= 500Optional bank account to register for the new organization. Uses the same schema as the bank account creation endpoint.
Organization created successfully
ID of the newly created organization
Display name of the organization
Account type the organization was created with.
personal, business Default partner fee in basis points for this organization