API reference.
Access information and a starting point for integration enquiries.
A clear starting point.
Public API documentation has not yet been published here. Contact the team to confirm whether an integration is available for your project and which technical reference applies.
Reference not yet published.
Base URLs, authentication instructions, endpoints, and code examples will need to come from the official API reference before implementation.
Start with your use case.
Describe what you want to build, the information you need, and how the integration would be used. The team can confirm what access is available.
Supported environments, access instructions, and credentials should accompany the documentation for any approved integration.
Documentation availability.
The following parts of the public reference are not yet published on this page.
| Reference | Availability |
|---|---|
| Base URL & version | Not published |
| Authentication & permissions | Not published |
| Endpoints & response schemas | Not published |
| Errors & rate limits | Not published |
| SDKs & webhook support | Not published |
Understanding simulation data.
Our platform is an educational simulation environment. Displayed balances, positions, rates, and outcomes are virtual.
When discussing an integration, identify the assumptions and units you need to work with, including currencies, time periods, and what each value represents.
Talk to the team.
Include your intended use case, preferred programming language, and the information or workflow you want to connect. For an existing approved integration, include its reference and a redacted error example.