Integration acceptance

Sandbox evidence required to accept a partner integration.

Follow Connect your data and insights and the data connection guide. Record evidence from your organization's sandbox before activating production.

Use a second organization for access checks and two portfolios with representative holdings. Record the API environment, connector hosting (and image digest when partner-hosted), mapping versions, event schema revision, SDK version where used, organization IDs and reference implementation revision. Run the same lifecycle for REST, TypeScript or Java; the broker transport remains the Motif connector in every case.

Test	Expected evidence	Owner
Authenticate	API key and source credentials select the intended organization and environment; foreign credentials cannot read its data or resources	Partner + Motif
Install	Released SDK, where used, installs cleanly; a Motif-hosted connection shows Ready on the Status tab, or the pinned partner-hosted connector image starts with mounted secrets and becomes ready	Partner + Motif
Discover assets	All catalog pages are considered; category, symbol, exchange and name resolve the correct listing, including ambiguous symbols	Partner
Map a listing	Asset master event maps the partner's listing reference to the verified Motif asset ID; exact reference lookup returns that identity	Partner + Motif
Create a custom instrument	Explicit CREATE_CUSTOM master yields one identity across retries; both books reuse it	Partner + Motif
Confirm processing	Each message from your source yields a durable APPLIED or REJECTED receipt; the receipt API reconciles a missing return event	Partner + Motif
Publish a price	Current-day CUSTOM price retains its decimal precision and currency; the receipt identifies the intended asset	Partner + Motif
Apply a correction	New event ID and higher revision correct the same observation; stale or conflicting revisions are rejected	Partner + Motif
Deduplicate	Identical event retries have one mutation and retain the original outcome; changed content under an existing event ID is quarantined	Partner + Motif
Recover missing master	Price waits for its master, then applies; a permanently missing master eventually returns MASTER_NOT_FOUND	Motif
Store FX	The dated MID observation is returned for the right pair and organization; no automatic portfolio conversion is assumed	Partner + Motif
Create two books	Distinct external account IDs create distinct portfolios; each accepted revision reconciles holdings, cash, prices and total once calculation is CURRENT and complete	Partner
Replace holdings	Revision 2 changes the intended quantities and cash and removes omitted holdings; identical retry has no duplicate effect	Partner
Revalue shared assets	An accepted price change eventually updates every affected active book without another snapshot PUT	Motif + Partner
Read insights	Market and asset reads work independently of portfolio creation; portfolio reads resolve the correct book, language and content dates	Partner
Receive publications	Eligible MARKET, ASSET and PORTFOLIO events arrive on the partner return queue; the consumer durably records them and fetches the right content before acknowledgment	Partner + Motif
Handle absent content	Missing research and unobserved publications are reported honestly; stale dates and incomplete valuations remain visible	Partner
Isolate notifications	Disabled subscriptions and unauthorized subjects receive no new queued publication deliveries; private asset research is not broadcast	Motif
Quarantine invalid input	Unreadable messages return to your quarantine exchange; readable messages that fail mapping or validation are counted as quarantined on the Status tab, get no receipt, and Preview reproduces the error at your source path; corrected payloads are republished	Partner + Motif
Recover source failure	Messages are not acknowledged at your source until Motif has them; restarts, unreachable sources and interrupted return delivery recover without silent loss	Partner + Motif
Isolate connections	Failure of one organization connection leaves other connections working; readiness reports the failed connection	Motif
Rotate credentials	Rotated source and API credentials reconnect successfully; pending events and receipts reconcile afterward	Partner + Motif
Close a book	Archive the intended account, stop its source snapshots and verify that future portfolio notifications are no longer eligible	Partner + Motif

Save sanitized event bodies, receipts, API requests/responses, IDs, revisions, timestamps and observed outcomes. Delivery to your source or broker does not prove application processing; an APPLIED price receipt does not prove completed valuation; a subscription does not prove that research was generated. Existing messages already delivered to a partner queue cannot be recalled when a subscription or access permission changes.

Completion

Accept transport, ingestion, valuation and content delivery separately. A local contract fixture validates the reference's requests but does not replace sandbox evidence against the deployed Motif API, feeds service and research workers.

This live contract accepts prices from the current UTC day. Historical imports, position profit/loss attributes and Illio backtesting require an agreed data contract and are not acceptance claims for this release. Stored FX does not enable cross-currency valuation. Record any additional product requirement explicitly before signing off.

The estimated 100,000 portfolios and 5,000 assets are sizing inputs. Agree peak update rates, holdings distribution, retention and recovery objectives; measure sustained ingestion, backlog recovery and valuation latency with representative load before production activation.

Production cutover

Provision the production organization, API key, source connection and credentials separately. Recreate mappings and subscriptions using production Motif IDs. Start with a representative batch, reconcile values and content routes, then increase volume within the agreed limits.

Monitor queue depth and age, quarantine counts, reconnections, pending receipts, valuation backlog and stale content. Retain accepted payloads and revisions for deterministic recovery, and test source backup/recovery and the agreed availability topology. Enabling the production connection sets up its own Motif virtual host. For a partner-hosted connector, the connector operations guide describes provisioning and runtime configuration.