US daily vs 5-minute volume mismatch + history_candlesticks 301607 limit:0 entitlement clarification
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 61
- Forks
- 30
- Merge medio
- 7 h 45 min
- PR fusionados (30 d)
- 17
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de longbridge/developers
-
最新版的Python 4.3.2 sdk 根本跑不通这个代码啊Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
longbridge/developers#1109 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
longbridge/developers#1314 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 1-2 días Aptitud para principiantes 45/100
longbridge/developers#1312 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 1-2 días Aptitud para principiantes 35/100
longbridge/developers#1310 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
LONGBRIDGE AI模型选择Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
longbridge/developers#1309 ·
Los mantenedores suelen responder en 1 día
Todos los issues de longbridge/developers
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Azure/azure-functions-nodejs-extensions#180 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 2 días
-
iso-bmff: add IsoBoxReadView.readUint64 and IsoBoxWriteView.writeUint64 for exact 64-bit fieldsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
streaming-video-technology-alliance/common-media-library#611 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
prime-radiant-inc/evener#5901 ·
Los mantenedores suelen responder en 1 día
-
area:frontend kind:bug priority:p3 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día