Enrich your core / CRM with user account data
Derive member-level attributes — account, balance, products held, KYC state.
Goal. Derive member-level attributes — has an investment account, has a balance, holds product X, KYC state.
Endpoint. Get user list (paginated) for a full sweep, or Get user detail for a single member.
Batch sweep.
- Page through Get user list: start with
last_record_number=0, then repeat with thelast_record_numberfrom each response until you have pulledtotal_recordsitems. - Narrow server-side where useful with
product, the per-product KYC filters, or thecreated_atwindow. - For each user, derive attributes from the payload (see table below).
- Upsert into the core/CRM keyed by
user_account_id.
| Attribute | Derivation |
|---|---|
has_investment_account | accounts is non-empty |
has_balance | total_current_market_value > 0 |
has_crypto / has_securities / has_robo / has_roth_ira | a matching entry exists in accounts |
<product>_market_value | that account's current_market_value |
kyc_pending | any account with kyc_status: pending |
Notes. Run as a scheduled batch (e.g. nightly). Compare decimals as decimals, not floats. A 404 on the single-user endpoint means no investment relationship — set the boolean attributes to false rather than failing.