Start
Connect, build, and test the first paper route.
Documentation
Run the full route.
Connect, test, protect, and trace every FirmGated workflow.
Start with one paper route
5 steps. One clean test.
Do not connect everything at once. Prove one route end to end.
Core path
See the gate work.
One alert enters. Each account gets its own checks and recorded result.
Follow an orderSourceTradingView1 JSON alert
FirmGatedRules checkedRoute · limits · approval
Route APassRoute BHoldRoute CBlock
Documentation map
Find the exact layer.
13 maintained guides. 11 live references.
Send
Format alerts and trace how an order moves.
Protect
Map account rules to checks, warnings, and blocks.
Prop Firm AccountsDaily limits, drawdown, sessions, and firm permission.Target LockWhat Target Lock does at your profit level, and how to send a close or flatten and lock request from a Pine alert or Python script.Custom RulesYour own limits on a Guardian account: daily loss, trades per day, max contracts and a trading window. Alerts only.Before You Go LiveA paper-first checklist and current platform limits.
Operate
Inspect alerts, records, connections, and account state.
Reference
Limits, maintenance, definitions, and support.
Request LimitsCurrent intake, safeguard, and sign-in limits.FAQVerified answers to common platform questions.GlossaryFirmGated terms in plain English.SecurityHow credentials, routes, and records are protected.PlansCurrent route capacity, asset access, and pricing.SupportWhat to include when a documented fix is not enough.
Coverage
The full operating loop.
Docs cover setup, control, evidence, and recovery, not only alert creation.
Read common questionsSmallest valid alert
3 fields. Start there.
ticker and action are required. quantity is optional and defaults to 1. The shorter qty alias is also accepted.
{
"ticker": "MNQ",
"action": "buy",
"quantity": 1
}