Technology product
ClonePips API
Programmatic access to the ClonePips platform. A public interface for building broker front-ends, integrating risk tooling and consuming platform data.
- Read access to strategies, performance and allocations
- Webhooks for trades, risk events and billing
- Scoped API keys per broker tenant
- Rate limits and sandbox environment
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
Availability
In development in this build
This product is designed but not released. Everything below describes the intended design and is marked accordingly.
- Listed in development in the product registry — not available today.
- Slated to deliver 2 platform modules, described on this page as design.
- Declared integrations: rest api, webhooks — none is connected in this build.
Registry facts
- Category: technology
- Status: In development — described as design
- Intended for: brokers, institutions, traders
- Delivers modules: 2
- Pricing basis: contact
Why it exists
Integrations should read the same records
A broker building a front-end does not want a parallel data model. Any integration that reconstructs platform state is a second source of truth that drifts from the first.
ClonePips API describes one tenant-scoped interface: read access to the published records the platform's own surfaces project, webhooks for trade, risk and billing events, and keys scoped and rate limited per tenant.
Because the interface reads the same published records, an external system shows what the platform shows, and a misconfigured client cannot read across tenants.
- Read access to strategies, performance and allocations.
- Webhooks for trades, risk events and billing.
- Tenant-scoped keys with rate limits and a sandbox.
Product view
The integration surface, illustrated
A service map of the intended API — read resources, event streams and a tenant-scoped request path — labelled demo data for interface development.
Platform API — service map
Demo dataService boundaries
- StrategiesRead
- PerformanceRead
- AllocationsRead
- Risk eventsEvents
- BillingEvents
Illustrative resource groups. No endpoint is live in this build.
Request path
- 01Client request presents a tenant-scoped key.
- 02Edge authenticates the key and applies rate limits.
- 03API layer reads the published records the surfaces project.
- 04Response is shaped by those same records, not a second model.
Integration surfaces
- Read endpointsDesigned
- Webhook deliveryDesigned
- Sandbox tenantLater
Performance figures shown on this site are illustrative demo data. Past performance is not indicative of future results.
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
- The frame maps service boundaries — read resources and event streams, not a console.
- It shows a tenant-scoped request path, from key to response, over the same published records.
- This product is in development; the frame is fictional demo data illustrating the intended design, and no endpoint is live.
- Illustrative product composition built from demo data. Not a live account or venue.
Design
How ClonePips API is designed to work
Read surfaces
External systems read the same published records the platform's own surfaces project.
Event delivery
Trade, risk and billing events are delivered to registered endpoints with delivery records.
Tenant-scoped keys
Keys are scoped to a broker tenant and rate limited, so a misconfigured client cannot read across tenants.
Workflow
ClonePips API end to end
How the pieces connect. The diagram names the stages; the labels live in configuration, like every other page.
A vertical slice through the stack: user experience surfaces, the core product engines, the execution layer and the trading platforms orders end up on.
1. User experience
4Surface each audience operates.
2. Core product
4Capabilities every surface shares.
Every surface talks to the same core
3. Execution
2Server-side routing and bridge.
Normalised orders and evaluations
4. Trading rails
3Where orders end up.
Routed to the venue's platforms
- The API exposes the same published records the surfaces project.
- Event delivery carries trade, risk and billing changes outward.
- Keys are scoped to a tenant and rate limited at the edge.
Deployment
Deployment notes
- 01
Step 1
Exposes read access to strategies, performance and allocations for broker front-ends.
- 02
Step 2
Publishes webhooks for trades, risk events and billing so external systems can react.
- 03
Step 3
Scopes API keys per broker tenant, with rate limits and a sandbox environment.
Questions
About ClonePips API
Is this product available today?
No. The product registry lists ClonePips API as in development. No public API endpoint ships in this build.
What would a sandbox environment provide?
A non-production target with synthetic data, so an integration can be built and tested before it is pointed at a venue — as designed, not as shipped today.
Notices
Risk warning
Trading foreign exchange, CFDs and leveraged instruments on margin carries a high level of risk and may not be suitable for all investors.
No advice
Information on this site is provided for general information only and does not constitute investment advice or a recommendation.
Demo data
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
Next
Discuss this product's place in your stack
Bring the venue, the execution setup and the fee model you run; the demo covers the platform and the commercial basis.