Scheduled Fire Jobs
| Symbol | Side | Qty | Type | Product | Fire Time (IST) | Lead ↓ | Burst 💥 | Profile | Status | Actions |
|---|---|---|---|---|---|---|---|---|---|---|
| No fire jobs yet | ||||||||||
Zerodha Profiles
🔑 Daily Token Refresh
- 1.Select a profile above, click "Get Login URL" — a Zerodha login link opens in a new tab.
- 2.Log in with your Zerodha credentials + TOTP. After login you'll be redirected to a URL like
https://...?request_token=XXXXXXXX - 3.Copy the
request_tokenvalue, paste it below, click "Activate".
Trade Log
| Symbol / Shot | Side | Qty | Local Fired At | Exchange Time | Order ID | Status | Message | Δ(ms) |
|---|---|---|---|---|---|---|---|---|
| No trades yet | ||||||||
⏱ Network Latency to Zerodha
How fire_lead_ms works
1. Set fire_time = target arrival
In your job, set fire_time to the exact time you want the order to land at Zerodha — e.g. 10:30:00.000.
2. Measure your latency
Click Measure below. The app sends 10 real API calls and measures round-trip time (RTT). One-way estimate = RTT ÷ 2.
3. Set fire_lead_ms
Use the recommended_lead_ms value in your job. The scheduler then fires that many ms early so the order arrives at fire_time.
After each order fires you'll see arrival_delta_ms in server logs — how many ms off from your target the exchange acknowledged it. Fine-tune fire_lead_ms until delta ≈ 0.
Min RTT
—
Avg RTT
—
Median RTT
—
P95 RTT
—
Max RTT
—
Recommended
—
fire_lead_ms
Set fire_lead_ms = ? on your job and change fire_time to the exact arrival time you want (e.g. 10:30:00.000).
Requires an ACTIVE access token on the selected profile. If your token is expired, validate it on the Profiles tab first.
User Management
| ID | Username | Approved | Admin | Registered | Action | |
|---|---|---|---|---|---|---|
| Loading... | ||||||