Overview

Strategy JSON structure

The top-level fields of a strategy document, what each one contains, and which are required.

1 min readUpdated Jun 19, 2026

A complete strategy JSON:

{
  "name": "RSI Mean Reversion",
  "version": "1.0",
  "timeframe": "1h",
  "indicators": [...],
  "trend_detection": {...},
  "entry_rules": {...},
  "entry_execution": {...},
  "exit_rules": {...},
  "risk_management": {...}
}

Required fields

FieldTypePurpose
namestringDisplay name
versionstringSchema version (e.g. "1.0")
timeframestring1m / 5m / 15m / 1h / 4h / 1d
indicatorsarrayIndicators to compute
entry rulesobjectLong / short conditions
exit rulesobjectStop loss, take profit, modifiers
risk managementobjectSizing + leverage

Optional fields

  • trend detection - when omitted, defaults to method: none.
  • entry execution - when omitted, defaults to market.

Validation

The engine validates the JSON before saving. Common rejections:

  • Unknown indicator type
  • Condition references an undeclared indicator name
  • Conflicting evaluate modes inside a single rule
  • Missing required params for the chosen sizing or stop type

The validator returns the first error it finds. Fix it and re-save; the engine doesn't accept partial saves.

Strategy JSON structure | Help Center | LucraX · LucraX