Account Management

We power CLOB trading account activation via REST API, allowing platforms to stand up funded accounts for approved participants and manage those accounts over their lifetime.

Flexible Funding Models

You have the ability to activate accounts under either funding model, selected at creation via the prefunded flag:

• Pre-Funded (prefunded: true): Customer USD balances are held at zerohash and ledgered directly to the customer. zerohash performs credit checks against the customer's on-platform USD balance, and the platform tops up via POST /transfers from its float account.
• Non Pre-Funded (prefunded: false): Customer USD balances remain on the platform's ledgers. The platform performs credit checks before submitting an order, and buying power draws from the platform's float upon execution.

Sequential Dependency

The endpoints work in tandem across the account lifecycle:

1. Create Participant: Platforms register the end participant via POST /participants/customers/new (individual) or POST /participants/entity/new (entity).
2. Confirm Approval: Verify the participant's status is approved via GET /participant/{participant_code}/basic_info before any account call.
3. Activate Account: Submit the approved participant_code and chosen funding model via POST /accounts. The response returns the account_group and account_label used for subsequent trading and lookups.
4. Retrieve & Update: Fetch account details via GET /clob/accounts/{account_id} and amend account attributes via PATCH /clob/accounts/{account_id}.

Configuration Review

Please review the different permutations of the API request body. It is vital to ensure your platform uses the intended parameters (e.g., individual vs. entity participant creation, prefunded: true vs prefunded: false, and the correct participant_code / account_group / account_label pairing) corresponding to your specific business logic to avoid funding and credit-check discrepancies on the CLOB.