Creating an entity
Overview
An Entity is DriveWealth's identity for a business or trust — the counterpart to a User for
individuals (see the Users API's Creating a user if you're onboarding a person, not a business/trust). Every business/trust Account maps back to exactly one Entity, and no Account can be opened until the Entity exists and clears KYB (Know Your Business).
Unlike individual onboarding, this isn't a single-API flow — it spans four APIs:
| Step | API | Call | Result |
|---|---|---|---|
| 1 | Entities | POST /entities | Entity created, status: PENDING |
| 2 | Documents | Physical Documents API | Formation documents uploaded (not covered here) |
| 3 | Users | POST /users (×N) | Each director/trustee/grantor/beneficiary created as INDIVIDUAL_TRADER, linked via DIRECTOR_INFO |
| 4 | Accounts | POST /accounts | Business/trust Account opened — userID on this call is the entity's id |
Which type of Entity do you need?
| Your use case | type | Guide |
|---|---|---|
| A corporation, LLC, or partnership opening a business trading account | CORPORATION / LLC / PARTNERSHIP | Onboarding a Business Entity |
| A trust (including an Australian SMSF) opening a trading account | TRUST | Onboarding a Trust Entity |
A
subTypeis required forCORPORATION/LLC/PARTNERSHIP, optional forTRUST. The only valid
subTypefor aTRUSTisSMSF(Australian Self-Managed Super Fund) — a standard trust omitssubTypeentirely.
Before you start
Every request needs a session token (or bearer token) and your app key, sent as Authorization: Bearer ACCESS_TOKEN (or dw-auth-token) plus dw-client-app-key on every call. See the Authorization docs for the full setup.
Updated 3 days ago