Improved
Account creation aligned by account type
September 9th, 2026
Broker API
POST /v1/accounts is now documented as a single flat request object whose requirements vary by account type, with named examples for inline trading, custodial, donor-advised, and existing-holder IRA requests.
- Documents per-type requirements: trading needs inline
identityandcontact(or an existing holder), custodial needsidentityandminor_identity, IRA needsaccount_sub_typeand US equity, and donor-advised needsentity_id. Omittingaccount_typestill defaults totrading. - Adds
entity_idandminor_identityto the account creation request schema. - Create requests accept the four public values
trading,custodial,donor_advised, andira; account responses now also document the runtime-reachable valuestrust,omnibus_non_disclosed,omnibus_sub,hsa, andjoint. - Documents creating an account for an existing holder with
primary_account_holder_idfor trading and IRA accounts. - Relaxes static
requiredoncontact,identity,disclosures, andagreementsso every documented creation flow is representable; conditional requirements are described in the schema and enforced by the server. - Corrects the HTTP 400 and 422 create responses to the structured
Errorobject withcodeandmessage: malformed or undecodable bodies return 400 with code40010000, and validation failures, including conflicting holder data, return 422 with code40010001. Generated clients may need updated response models. - Corrects the immutable
primary_account_holder_idbehavior onPATCH /v1/accounts/{account_id}: supplying a different value returns HTTP 403, now documented with its error response. - Marks
tax_id_typeas required on the custodial minor identity schema and clarifiesTrustedContact, which requires at least one ofemail_address,phone_number, orstreet_address.
Affected Endpoints
POST /v1/accountsGET /v1/accountsGET /v1/accounts/{account_id}PATCH /v1/accounts/{account_id}