Plan your integration

Choose an integration with Motif, agree the data contract, and work through a pilot together.

Start with the experience you want to give your clients and a representative portfolio. We will help you choose the integration, check instrument and price coverage, and work through a test implementation before rollout.

Begin by answering the project kickoff questionnaire before the kickoff meeting. Then use Connect your data and insights for subscriptions, market and asset reads, portfolio examples and the sandbox-to-production checklist. The SDK and REST reference implementations run that guide step by step. The lifecycle overview summarizes the relationships.

Choose your starting point

What you want to deliver	Start here	What you provide
Portfolio data, asset prices and master data in; market, asset and portfolio insights out	Connect your data and insights	Anonymized portfolios, dated valuations, instrument identities, a data source (REST API, message broker or file drop) and a notification channel (broker output or HTTPS webhook)
A portfolio app with current holdings, values and scheduled calculations	Portfolio data feed	Complete holdings snapshots, cash and the agreed dated valuations
Non-US listed holdings	Non-US holdings	Exact exchange listings, share classes, quantities and agreed price coverage
Non-listed holdings and private funds, including PE and VC funds	Non-listed and private holdings	Fund or vehicle identity, actual units held and dated unit NAVs
Non-standard equity, such as direct private-company shares or bespoke interests	Agree a private holding mapping	Security terms, ownership units and valuation basis for review with Motif
Non-standard crypto or other externally held crypto	Non-standard crypto	Stable instrument IDs, network details, quantities and dated prices
Clarity chat or an embedded research experience inside your existing app	Portfolio context, then Integrate Clarity or Embed Clarity	Holdings context and, where useful, recent trades and investor context
Market or asset research without maintaining client portfolios in Motif	Quickstart, then Integrate Clarity	The requested market or asset and language

Choose the relevant path for each holding; these are not mutually exclusive portfolio categories. A mixed portfolio can use the same snapshot contract for supported instrument types. We review currency and valuation coverage across the whole book. Creating a native portfolio does not automatically create a Clarity partner context, bind a user or enable an embed; agree those connections with Motif when combining experiences.

Decide between snapshots and trades

Start with snapshots when your system already knows the current positions. You send the complete book each time it changes. Motif replaces its holdings and recalculates. This is the starting point for the listed, private-fund and crypto walkthroughs.

Bring a transaction requirement to the design discussion when you need realized returns, tax lots, distributions, or cash-flow-aware performance. The native snapshot API does not ingest a transaction ledger. Clarity's separate partner context accepts recent trades for research context, but does not turn those trades into native portfolio accounting. We agree the required accounting and data contract before you build that part.

Agree a small pilot with us

Answer the project kickoff questionnaire and share it, with the following, through the onboarding channel agreed with Motif:

Bring to the discussion	We decide together
One representative portfolio, including an unusual instrument	Which instrument identities and valuations are needed
The system supplying positions, such as your portfolio administrator or custodian	Who owns the current holdings and how updates arrive
Your price source and its observation timestamps	Which prices you supply, which Motif can fetch, and where history is available
Required currencies and analytics	Whether the current single-currency snapshot contract meets the use case
Your desired client experience	Your own UI, the Motif portfolio app, Clarity embed, or a combination
Your data sources (REST API, message broker or file drop) and network policy	How Motif's connector collects your data, and partner hosting where your policy requires it
Expected portfolio count and update frequency	A delivery schedule, API allowance and recovery process

Leave this discussion with an agreed instrument mapping, price responsibilities, connector hosting and connectivity, pilot environment, available API/SDK version/artifact that passes the capability check and acceptance criteria. Endpoint availability and market-data coverage must be confirmed for that environment before implementation.

Work through the implementation

1. Map your data using the non-US holdings, non-listed and private holdings, and non-standard crypto examples that apply to your book.

2. Implement the sender, receiver and reader from Connect your data and insights, then record integration acceptance.

3. Review the results with Motif, connect the client experience, and agree the production rollout.

Keep the snapshot reference alongside the walkthrough for exact field rules and error responses.