Technical documentation for engineers integrating WealthArc, and a sandbox for data teams who want to judge our coverage and data quality before anyone signs anything.
We will stand up an isolated sandbox tenant loaded with data from the custodians you name. Reconcile it against your own records, run your own quality checks, point your own pipelines at it. No production commitment, no data of yours required to start.
A read-only REST API over data we have already consolidated, reconciled, and normalised. One API key in an x-api-key header, then query portfolios, positions, transactions, assets, and daily metrics. It speaks OData, so you filter and pick your fields on the server and take only what you need.
Every position comes back in the same shape whichever bank it came from. Identifiers are resolved, the FX rate is attached with its source, and the valuation in each currency you report in is one $expand away.
Values are illustrative. Read the full reference for the authoritative field list.
// GET /v1/Positions // ?$filter=portfolioId eq 4182 // &$expand=values // &$top=50 // x-api-key: <your key> { "@odata.count": 37, "value": [ { "id": 90418822, "portfolioId": 4182, "assetId": 615204, "statementDate": "2026-07-30", "quantity": 1500, "price": 275.00, "priceCurrency": "CHF", "portfolioCurrency": "USD", "fxRate": 1.0811, "fxRateSource": "WealthArc", "allocation": 0.0642, "values": [ { "amount": 445953.75, "currency": "USD", "fxRate": 1.0811 } ] } ] }
Authentication, the OData parameters, and every endpoint, with response schemas and samples for each. Public, no key needed to read it.
Open the reference →The machine-readable definition of the API. Point your generator at it and you have a typed client, in whichever language you work in, before you write a line yourself.
Download v1.json →The full specification of the normalised investment data schema behind the API: entities, field-level definitions, enumerations, and how each custodian's quirks are mapped onto it.
Request access →A Model Context Protocol server that exposes the same data as tools, so any MCP-compatible agent framework can query portfolios directly without a bespoke integration.
Request access →For teams that would rather not poll: the same normalised data delivered as files to your own storage on a schedule you set, instead of pulled endpoint by endpoint.
Request access →Which custodians are connected, in which jurisdictions, and what each feed carries. Check whether your banks are already live before you write any code.
Explore Connectivity →Tell us what you are building and which custodians matter. We will get you credentials and someone who can answer technical questions directly.