Kite console

Kite token, instrument master, and the group quantity settings. Trading itself is untouched here.

Status

Kite credentialsijivgh… configured Access tokentoken present d2y9RJUb1A… (13h 24m left) Redis keykite_access_token Instruments119160 (119111 non-SPOT) Redirect URLhttps://kite.awesomefxmarkets.com/callback

1. Kite access token

Log in to Kite Kite login → https://kite.awesomefxmarkets.com/callback → token in Redis, picked up by stock-socket live
  1. That URL must be the redirect URL registered in your Kite app.
  2. Tokens expire every morning around 07:30 IST - come back and click again.

It is checked against /user/profile before it is stored, so a wrong or expired token is refused. Storing publishes it on kite_access_token, which is how stock-socket picks it up without a restart.

2. Instruments

idle

3. Groups & quantity settings

These are the rows the order path reads: groupsettings (per-order lot limits, looked up by segment + script + group_name) and optionally script_limits (margin / brokerage for one user).

groupquantity settingsclientsstatus
DEMO 15238 1 active
sets group_id + one assigned_group entry per segment of that group

4. Account type (NETTED / HEDGE)

How the client's book is closed. NETTED - one position per script, closed as a whole. HEDGE - every fill is its own ticket, each closed separately. It is a flag on usermodalnew.account_type, not a data migration: the client reads it with every position, so the change shows up on the next update (no restart).
Now: HEDGE: 1 · NETTED: 2