Intake APIs¶
Bringing trades, market data, reference data, and runtime config into the platform.
The platform is intake-first: data enters as governed submissions that are validated and translated. The Phase-1 control-plane API is the dedicated intake surface. Available today.
Submit Data¶
| Operation | Submits |
|---|---|
phase1IntakePortfolioTrades |
Trades and portfolio composition |
phase1IntakeMarketSnapshots |
Market data snapshots (curves, parameters) |
phase1IntakeReferenceLegal |
Counterparty / legal / agreement reference data |
phase1IntakeRuntimeConfigs |
Runtime configuration packs |
Each intake call accepts the relevant artifacts and returns an operation handle; intake is processed asynchronously.
Inspect What Arrived¶
| Operation | Returns |
|---|---|
phase1ListArtifacts |
Artifacts received |
phase1GetArtifact |
A single artifact |
phase1GetArtifactVersions |
Version history for an artifact |
phase1GetArtifactValidationIssues |
Validation findings on a submission |
phase1GetArtifactTranslationReport |
How the input was interpreted |
phase1ListProfiles |
Available intake/translation profiles |
Preview A Run Before Committing¶
| Operation | Purpose |
|---|---|
phase1BuildRunPreview |
Build a preview of what a run would do |
phase1GetRunPreview |
Retrieve the preview |
Track Intake Work¶
| Operation | Purpose |
|---|---|
phase1GetOperation |
Status of a long-running intake operation |
phase1GetJobStatus |
Job-level status |
A Note On Per-Entity CRUD¶
If you expected createTrade / createMarketDataCurve, note that those are
idealized names, not the delivered API. The governed path is the
submission-based intake above. Direct per-entity REST endpoints are roadmap — see
API Surface & Evidence.
What This Means For Integration¶
- Batch your data into submissions; do not look for row-by-row writes.
- Always read the validation issues and translation report before proceeding — they tell you exactly how your input was understood.
- Use run preview to de-risk before you commit compute.