Introduction - TetraFi

Everything your workspace has traded, read-only: filtered lists, single-trade timelines with settlement evidence, bulk exports, one surface across all chains.

Where It Fits

After-the-fact answers - fill reconciliation, volume tracking, flow audits
No explorer archaeology - one query surface replaces per-network indexing
One record across the layers (coming soon) - a settlement opted into Multilateral Netting keeps its trade record here and gains a per-run statement (integration shape)

Quick Reference

Facet
Protocol	REST over HTTPS
Credential	API key or JWT bearer - workspace scoping is automatic
Base URL	`https://api.tetrafi.io/api/v1/workspaces/{id}/`
Effort	Light: plain GET requests, nothing to sign

Endpoint Map

Endpoint	Purpose
`GET /api/v1/workspaces/{id}/trades`	List and filter trades: route legs, LP, settlement facts, offset pagination
`GET /api/v1/workspaces/{id}/trades/{orderId}`	One trade in full: amounts, status, settlement txs
`GET /api/v1/workspaces/{id}/trades/export`	Bulk CSV export for reconciliation and reporting

Under the same prefix: .../trades/{orderId}/timeline (hash-chained lifecycle), .../trades/{orderId}/evidence (compliance evidence bundle), and .../trades/mine, .../trades/mine/{orderId}, .../trades/mine/{orderId}/timeline for the caller’s own trades only. Your API key scopes every answer to your workspace.

Quickstart

Your first history query.