Resources / Integration
Integration and API architecture
GIGX exposes a small number of well-defined service boundaries. Each is provider-backed, so a demo provider can be replaced by a live one without changing the product experience.
Service interfaces
| Interface | Responsibility | Demo provider |
|---|---|---|
| Market data | Quotes, indices, movers, historical series, company data | Simulated series |
| Orders | Order creation, validation, lifecycle transitions, executions | Simulated matcher |
| Portfolio | Positions, cash, valuation, performance, dividends | Platform ledger |
| Identity & KYC | Verification checks and status | Simulated verification |
| Payments | Funding and withdrawal instructions | Simulated rails |
| Compliance | Eligibility evaluation, disclosures, restrictions | Platform rules |
| Notifications | Order, portfolio, risk, compliance and account messages | In-platform delivery |
Replacing a provider
Product code depends on the interface, never on a concrete provider. Connecting a live market-data feed or a broker order-management system means implementing the interface and changing configuration - the investor experience, risk engine and audit trail continue to work unchanged.
Every call crosses a server boundary where authentication, authorisation and validation are applied. No provider credential is ever present in client code.
Speak with the GIGX team
We work with licensed brokers, investment firms and market infrastructure operators.