Market, Trade, Config, And API Guide¶
How you bring data in, configure runs, execute, and consume results.
The platform is headless and contract-first: everything the workbench does, your systems can do through the same typed APIs. There is no privileged path that bypasses governance. Available today.
How Data Enters: Governed Submissions¶
Market data, trades, portfolios, and reference data enter as governed submissions that are validated and translated into canonical objects on the way in. This is a deliberate choice — it means nothing reaches your analytical truth without being validated and evidenced. Available today.
flowchart LR
A[Upload artifacts] --> B[Create submission]
B --> C[Translation to canonical objects]
C --> D[Readiness evaluation]
D --> E[Approval]
E --> F[Governed run]
F --> G[Results and evidence]
You can submit and inspect:
| You can | Today |
|---|---|
| Submit portfolio and trade data | Available |
| Submit market data snapshots (curves, parameters) | Available |
| Submit reference, legal, and agreement data | Available |
| Submit runtime configuration | Available |
| Inspect submitted artifacts, versions, and validation findings | Available |
| Retrieve the translation report — how your input was interpreted | Available |
| Preview a run before committing | Available |
On the roadmap: direct per-entity REST endpoints (for example, creating a single trade or curve directly) will sit alongside today's submission-based intake for teams that prefer them.
Canonical Objects And Compliance¶
Once translated, you can retrieve the resolved canonical control objects, enumerate canonical trades, and inspect the compliance packs and validators that apply. Your raw input and the platform's interpretation of it are both inspectable. Available today.
Configuration And Readiness¶
The Config Doctor APIs let you open a readiness case, validate configuration, get deterministic repair recommendations, compare configurations, and produce an evidence bundle — all programmatically, returning the same clear gate outcomes your teams see in the workbench. Available today.
Governance, Execution, And Results¶
| You can | Today |
|---|---|
| Evaluate run readiness | Available |
| Run the approval and waiver workflow | Available |
| Request a governed run | Available |
| Run from a reference-pack scenario | Available |
| Read governed analytical rows and result projections | Available |
| Open, refresh, and report on explainability insight cases | Available |
| Schedule recurring insight refresh | Available |
Analytical Retrieval¶
Your analytical truth in BigQuery is reached today through governed result rows and output projections. Available today. A dedicated analytics-retrieval and BI embedding API for ad-hoc governed querying is on the roadmap.
How You Integrate¶
- All calls go through a governed API gateway with policy control and tenant-scoped identity.
- The surface is fully typed (OpenAPI).
- Long-running operations return a handle you can poll to completion.
- Everything that enters is validated and evidenced — there is no raw write that bypasses governance.
What This Means For You¶
- Integrate once, govern always. The same typed APIs power your systems and the workbench.
- Quality is enforced at the door, because intake is validated and translated before anything is stored.
- You consume governed facts, not raw folders, so what your systems read matches what your people see.
Where The Platform Is Today¶
Submission-based intake, canonical objects, Config Doctor, governance, execution, results, and insight-case APIs are available today. Per-entity REST CRUD, run templating/scheduling APIs, and a dedicated analytics-retrieval/BI API are on the roadmap — see Capability Maturity And Status.