Summary
My Longbridge Developers paper account is registered in the Singapore region and is identified by the API as lb_papertrading.
Although the official documentation states that paper accounts support real-time A-share market data, my account currently receives CN quotes and 1-minute candlesticks with a consistent delay of approximately 15 minutes.
The Developer Center also explicitly shows only:
CN — 15-minute delayed quotes
There is no option visible for enabling real-time CN OpenAPI quotes.
I only need read-only real-time quotes and 1-minute candlestick data for market analysis. I do not require trading functionality.
Environment
- Account region: Singapore
- Account type: Paper Trading (
lb_papertrading)
- Authentication: OAuth authorization generated while the paper account was selected
- Access methods tested: Longbridge ChatGPT App and hosted MCP/OpenAPI
- Test symbol:
513310.SH
- Test date: August 27, 2026
- Time zone: UTC+8
- Trading functionality used: None
The connection successfully returned the paper account's cash information and empty positions, confirming that the authorization was bound to the paper account rather than my previous live-account authorization.
Steps to reproduce
- Select and authorize the Singapore paper account.
- Connect through the Longbridge ChatGPT App / hosted MCP.
- Query the CN market status.
- Query the latest quote for
513310.SH.
- Query the latest 1-minute candlesticks for
513310.SH.
- Compare the returned timestamps with the actual China market time.
Actual result
At the time of testing, the following timestamps were observed:
| Item |
Returned time |
| Actual China market time |
15:02:34 (UTC+8), market already closed |
| Market time visible through the delayed feed |
14:47:34, still shown as trading |
Latest quote timestamp for 513310.SH |
14:47:29 |
| Latest 1-minute candlestick |
14:47 |
The quote and candlestick data were therefore approximately 15 minutes behind the actual market time.
During the same session, NVDA.US returned current overnight-market data up to 14:54:43 (UTC+8), rather than exhibiting the same fixed 15-minute delay. This suggests that the MCP connection and OAuth authorization were functioning normally.
Developer Center permission
The quote-permission page for this paper account shows CN market access only as:
15-minute delayed quotes (CN)
It does not show a CN LV1 real-time OpenAPI package such as:
CN_L1_ChinaMainland_EL | LV1 Real-time Quotes
Expected result based on the documentation
The official General Q&A states:
The paper account supports real-time quotes for HK, US, and A-share markets.
It also states under the supported paper-account markets:
Supports real-time market data for Hong Kong stocks, US stocks, and A-share markets.
Documentation:
The official Quote API Overview states that the Basic OpenAPI quote level includes:
Documentation:
Therefore, I expected the SG paper account to receive real-time CN LV1 quotes and real-time 1-minute candlesticks.
Questions
-
Does the documented real-time A-share market-data support for paper accounts also apply to Singapore-region paper accounts?
-
Should an SG paper account receive the CN_L1_ChinaMainland_EL real-time quote package under Basic OpenAPI activation?
-
Why does my Developer Center show only 15-minute delayed CN quotes, with the API data delayed by the same amount?
-
Could this be an account-entitlement or backend configuration issue? If so, could the quote permissions for this paper account be checked and corrected?
-
If SG paper accounts are intentionally excluded from real-time CN OpenAPI quotes, could you clarify the applicable regional/account restrictions and update the documentation accordingly?
-
If an additional quote package must be activated, please provide its exact name, activation path, eligibility requirements, and pricing. I only require CN real-time quotes and 1-minute candlesticks.
Related issue
Issue #1167 reports a very similar symptom in another market: an account expected to have real-time OpenAPI quotes received data delayed by exactly 15 minutes.
That issue also shows CN_L1_ChinaMainland_EL | LV1 Real-time Quotes in the user's available quote packages, indicating that real-time CN OpenAPI access is available for at least some accounts.
Additional information available
For privacy reasons, I have not posted my full paper-account ID or any OAuth credentials publicly.
I can provide the following if needed:
- Full paper-account ID through a private support channel
- A redacted screenshot of the Developer Center quote-permission page
- Redacted
longbridge auth status output
- Full redacted results from the market-status, quote, and candlestick requests
- Exact timestamps and additional CN symbols for reproduction
Please let me know the appropriate private channel if account-specific information is required.
Summary
My Longbridge Developers paper account is registered in the Singapore region and is identified by the API as
lb_papertrading.Although the official documentation states that paper accounts support real-time A-share market data, my account currently receives CN quotes and 1-minute candlesticks with a consistent delay of approximately 15 minutes.
The Developer Center also explicitly shows only:
There is no option visible for enabling real-time CN OpenAPI quotes.
I only need read-only real-time quotes and 1-minute candlestick data for market analysis. I do not require trading functionality.
Environment
lb_papertrading)513310.SHThe connection successfully returned the paper account's cash information and empty positions, confirming that the authorization was bound to the paper account rather than my previous live-account authorization.
Steps to reproduce
513310.SH.513310.SH.Actual result
At the time of testing, the following timestamps were observed:
15:02:34(UTC+8), market already closed14:47:34, still shown as trading513310.SH14:47:2914:47The quote and candlestick data were therefore approximately 15 minutes behind the actual market time.
During the same session,
NVDA.USreturned current overnight-market data up to14:54:43(UTC+8), rather than exhibiting the same fixed 15-minute delay. This suggests that the MCP connection and OAuth authorization were functioning normally.Developer Center permission
The quote-permission page for this paper account shows CN market access only as:
It does not show a CN LV1 real-time OpenAPI package such as:
Expected result based on the documentation
The official General Q&A states:
It also states under the supported paper-account markets:
Documentation:
The official Quote API Overview states that the Basic OpenAPI quote level includes:
Documentation:
Therefore, I expected the SG paper account to receive real-time CN LV1 quotes and real-time 1-minute candlesticks.
Questions
Does the documented real-time A-share market-data support for paper accounts also apply to Singapore-region paper accounts?
Should an SG paper account receive the
CN_L1_ChinaMainland_ELreal-time quote package under Basic OpenAPI activation?Why does my Developer Center show only 15-minute delayed CN quotes, with the API data delayed by the same amount?
Could this be an account-entitlement or backend configuration issue? If so, could the quote permissions for this paper account be checked and corrected?
If SG paper accounts are intentionally excluded from real-time CN OpenAPI quotes, could you clarify the applicable regional/account restrictions and update the documentation accordingly?
If an additional quote package must be activated, please provide its exact name, activation path, eligibility requirements, and pricing. I only require CN real-time quotes and 1-minute candlesticks.
Related issue
Issue #1167 reports a very similar symptom in another market: an account expected to have real-time OpenAPI quotes received data delayed by exactly 15 minutes.
That issue also shows
CN_L1_ChinaMainland_EL | LV1 Real-time Quotesin the user's available quote packages, indicating that real-time CN OpenAPI access is available for at least some accounts.Additional information available
For privacy reasons, I have not posted my full paper-account ID or any OAuth credentials publicly.
I can provide the following if needed:
longbridge auth statusoutputPlease let me know the appropriate private channel if account-specific information is required.