☰
›

[Bug] Discrepancy in last_price (NAV) between Kite Web Holdings and Kite Connect API (GET /mf/holdin

gvrcreddy
gvrcreddy in Python client
Hi Kite Connect Team,

I noticed a pricing/NAV discrepancy in Mutual Fund holdings between the **Kite Web GUI** (`kite.zerodha.com/holdings`) and the **Kite Connect API** (`GET https://api.kite.trade/mf/holdings`).

For example, for **Parag Parikh Flexi Cap Fund - Direct Plan** (ISIN: `INF879O01027`):

- **Kite Web GUI (Holdings):** Shows LTP / NAV = **`₹89.740`**
- **Kite Connect API (`/mf/holdings`):** Returns `last_price` = **`₹89.2332`**

API Response snippet:
```json
{
"tradingsymbol": "INF879O01027",
"fund": "PARAG PARIKH FLEXI CAP FUND - DIRECT PLAN",
"last_price": 89.2332
}
```

The Kite Connect API appears to be serving a stale NAV (from Friday, Oct 30) that lags behind what Kite Web / Coin is currently displaying (Monday, Nov 2 NAV).

Could you please check why `/mf/holdings` is not reflecting the latest NAV available on the web portal?
Tagged:
Sign In or Register to comment.