US daily vs 5-minute volume mismatch + history_candlesticks 301607 limit:0 entitlement clarification
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
Direzione di ricerca
Start by reviewing the referenced issues #1216, #1191, #913, #849, and #662, then check the documentation for candlesticks(count=1000), history_candlesticks_by_date, and history_candlesticks_by_offset. Done means documenting the applicable entitlement and quota behavior, the volume-data contract, and whether an upgrade changes either behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Longbridge Customer Services referred this technical question to this repository.
I am validating a read-only US-equity intraday research workflow through the connected Longbridge OpenAPI/MCP tools and need clarification on two reproducible data-contract/entitlement issues.
No credentials, account identifiers, tokens, or trading permissions are included here.
1. Daily vs complete 5-minute volume/turnover mismatch
Instrument: VTI.US
Adjustment: no forward adjustment
5-minute candles: trade_sessions=all (Overnight, Pre, Intraday, Post)
2026-09-23
- Native daily candle volume: 2,581,335 shares
- Native daily candle turnover: 978,481,653
- All 288/288 completed 5-minute bars from 04:00 UTC Sep 23 to 04:00 UTC Sep 24:
- summed volume: 1,929,865 shares
- summed turnover: 731,429,163.447
- 5-minute totals are approximately 74.76% of the daily totals.
2026-09-24
- Native daily candle volume: 2,600,775 shares
- All 288/288 completed 5-minute bars:
- summed volume: 1,759,623 shares
- 5-minute volume is 67.66% of the daily volume.
Similar discrepancies have appeared on other liquid US symbols.
Could the Longport team please confirm:
- The exact venue/tape and eligible trade-condition coverage of daily vs 1m/5m bars.
- Whether off-exchange/TRF trades, odd lots, auctions/crosses, delayed trades, or corrections are treated differently between daily and intraday candles.
- Whether daily candles can be updated with trades/corrections that are not propagated to minute candles.
- Whether there is a documented same-source normalization or alternative OpenAPI endpoint that can provide a consistent regular-hours 5-minute time-of-day volume baseline and ADV20.
2. Historical candlestick entitlement returns 301607 with limit:0
The connected account can retrieve recent candlesticks(count=1000) 5-minute data and 20 daily candles, but history_candlesticks_by_date returns:
301607
history candlestick symbol count out of limit
requested:0/limit:0
Additional reproduction from 2026-09-28:
NVDA.US, native unadjusted RTH 5-minute request: recentcandlesticks(count=1000)provided only 12 fully completed prior sessions.history_candlesticks_by_offsetlooking further back returned an empty list without an explanatory error.history_candlesticks_by_dateforNVDA.US, 2026-08-28 through 2026-09-09, returned 301607 requested:0/limit:0.
I found existing issues including #1216, #1191, #913, #849 and #662 concerning historical-candlestick quota/301607.
The limit:0 behavior therefore appears to be a known class of issue, but I still need clarification on the exact entitlement applicable to the connected account and whether a paid entitlement changes it.
Please clarify:
- Is date-range/offset historical access a separate entitlement from recent
candlesticks? - How can the live remaining monthly symbol/history quota be checked programmatically?
- What current entitlement or upgrade is required to retrieve at least 20 completed US RTH 5-minute sessions for a bounded personal research universe of roughly 8–20 symbols?
- If there is a paid tier, what is the current monthly all-in price and does the existing OpenAPI/MCP connection inherit the upgraded permissions without replacing credentials?
- Critically, would such an upgrade affect only historical depth/quota, or would it also change the daily-vs-minute volume/tape discrepancy described above?
The purpose is data validation only. I do not want to infer that purchasing a higher entitlement would fix the volume-population inconsistency unless Longport confirms that explicitly.
Thank you.
- Lingua principale
- TypeScript
- Stelle
- 61
- Fork
- 30
- Merge medio
- 7h 45m
- PR unite (30g)
- 17
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di longbridge/developers
-
最新版的Python 4.3.2 sdk 根本跑不通这个代码啊Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
longbridge/developers#1109 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
longbridge/developers#1314 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 1-2 giorni Idoneità per principianti 45/100
longbridge/developers#1312 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 1-2 giorni Idoneità per principianti 35/100
longbridge/developers#1310 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
LONGBRIDGE AI模型选择Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
longbridge/developers#1309 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di longbridge/developers
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
WalletConnect/walletconnect-monorepo#7392 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
fehler
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Azure/azure-functions-nodejs-extensions#180 ·
I maintainer di solito rispondono entro 1 giorno
-
bug good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
laaielichter/Threesmith#28 ·
I maintainer di solito rispondono entro 1 giorno