Structured market intelligence for subscribers, tools, and platform integrations
The iFX API is the outward-facing distribution layer for normalized analytical outputs. It is designed for browser applications, future terminal connectors, automation stacks, and external consumers that need structured access to signals, capital flow, and derived market state.
Built For
- platform users consuming analytics through iFX applications
- subscribers who need direct API access
- future MT4, MT5, and cTrader connector workflows
- automation and quant-style integrations
- future websocket-driven event transport
Platform Role
- feed.ifx.trading = ingestion layer
- api.ifx.trading = normalized distribution layer
- markets.ifx.trading = user-facing application layer
- ws.ifx.trading = future real-time transport layer
Current API Outputs
- latest signal state
- signal history
- capital flow state
- currency score normalization
- dominant flow direction
- future opportunity ranking outputs
Live Endpoints
Access Model
- Platform Access = browser-based application access through iFX front-end products
- API Access = direct endpoint access for approved subscribers and tools
- Connector Access = future terminal connector entitlement for MT4, MT5, and cTrader workflows
Authentication Direction
Protected routes currently use temporary query-string API keys during development. The long-term direction is database-backed keys, plan entitlements, rate limits, and controlled integration access by subscriber tier.
{
"auth_mode": "temporary",
"current_method": "query_string_api_key",
"future_direction": "db_backed_keys + entitlements + rate_limits"
}
Planned Subscription Tiers
- basic API access
- core endpoint availability
- lower request limits
- intended for evaluation and light tooling
- expanded API access
- higher request limits
- greater historical depth
- intended for active users and platform extensions
- full feature entitlement direction
- priority access to advanced outputs
- future websocket and connector alignment
- intended for serious integration workflows
Subscriber Direction
- web-first access for platform users
- direct key-based API access for external consumers
- future websocket access for lower-latency delivery
- future local connector support for terminal integrations
- plan-based access by feature, rate, and output scope
Example Flow Response
{
"flows": [],
"currency_scores": {
"EUR": 0.72,
"USD": -0.41,
"JPY": 0.11
},
"dominant_flow": {
"from": "USD",
"to": "EUR",
"value": 1.13
}
}
Integration Direction
- markets.ifx.trading platform modules
- subscriber dashboards and tooling
- future MT4 / MT5 / cTrader connectors
- automation pipelines and external applications
- future websocket event publishing
Request API Access
API access is currently provisioned on a per-subscriber basis. If you are building a tool, connector, or platform integration, request access below and include a brief description of your intended use.