Skip to main content

History, alerts, Terminal and SDK availability

Check separate access and rollout boundaries before building on advanced capabilities.

Advanced contracts are documented so you can assess an integration. A published guide does not activate the capability for your workspace.

History and exports

History and file exports require separate grants and source-purpose review. Retained ranges are recorded evidence, not proof of continuous coverage. Opening, closing and as-of results use original evidence and can be explicitly missing. See History.

Alerts and outbound delivery

Line-move alerts require separate alerts/odds access and approved destinations and source-use reviews. General customer production outbound delivery is not enabled automatically. Receivers must handle duplicate deliveries. See Alerts.

Terminal

Terminal uses signed-in session authentication and a separate product grant, rather than your API key or REST credit pool. Restricted internal access is not general customer availability. A comparison view does not establish settlement equivalence or an executable opportunity.

SDK packages and in-play

Python and TypeScript SDKs remain private preview artifacts, with no public npm/PyPI release. Use standard HTTP quick starts unless you have a separately supplied supported artifact. Current working collection is pre-match; synthetic in-play tests do not establish a live feed.

Review Current availability and contact support about the scope you need.

Did this answer your question?