Obtain and manage access tokens via OAuth 2.0 Client Credentials. Send grant_type=client_credentials with your client_id and client_secret. Use the returned access_token in Authorization: Bearer <token>. Tokens are short-lived—reuse during validity and renew on expiry.

Accounts hold investor positions, balances, and cash movements under a client. Endpoints let you list accounts, fetch details, and close accounts. Responses include status, owner info, currency, linked bank accounts, positions, and timestamps.

A client is your legal entity (B2B) or grouping for end-investor accounts. Use these endpoints to list, create, read, and update clients, manage bank accounts and service types, and fetch client-specific resources (instruments, custodians).

Fetch custodians linked to a client—useful for transfer instructions and operational routing. Returns identifiers and names for display and validation.

Journeys are secure, hosted web flows for customer interactions: account opening (e-sign), KYC/KYB questionnaires, fund transfers, and allocation plan setup. Create a Journey via API, redirect customers to the time-limited URL, and poll/callback for results.

The instrument universe consists of mutual funds available for a given client or globally. Retrieve instrument metadata: identifiers (e.g., ISIN), currency, latest price, KIID links, tradability flags, unit decimals, minimums, and cost/fee breakdowns.

Payment instructions (e.g., autogiro) batch one or more payments to accounts. Create instructions, then track the payments under each instruction (amounts, status, and references).

Fund orders (subscription/redemption) drive the trading lifecycle. Create, read, list, and cancel orders; track status from received → sent → confirmed → settled. Orders reference accounts and instruments, and map to cash/fund transactions on settlement.

Transactions record movements of money and units.

• Cash transactions (CT): deposits, withdrawals, cash legs of fund orders (with settlement dates).
• Fund transactions (FT): unit movements from subscriptions/redemptions (trade & settlement dates). Use these endpoints to reconcile ledgers and statements.

Receive real-time updates from Fondo without polling.

• WebSocket: open a persistent stream for .create, .update, .delete, and heartbeat events.
• Webhooks: register a callback URL to get signed POSTs with current/previous payloads. Include replay/retry handling in your consumers.