Technical Contract Clarification: Longport capital_flow Unit, Currency, Scale, and Turnover Compatibility

Aperta
  • Qualcosa non va?
#1,260 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, backend-api-design, documentation

Direzione di ricerca

Esaminare la documentazione ufficiale di CLI e le interfacce QuoteContext.capital_flow, quote e candlestick citate nell’issue, insieme ai percorsi SDK e Hosted MCP. Il lavoro è completato quando una dichiarazione autorevole e versionata conferma la semantica delle serie, le unità, la valuta, la scalabilità, la compatibilità e le eventuali trasformazioni, oppure identifica dove è documentato questo contratto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation question

Hello Longport Technical Support,

We are integrating the official Longport Hosted MCP capital_flow output into a fail-closed, read-only validation workflow.

The official CLI documentation states that each bar represents the net inflow for that minute. We have also verified from the official CLI, MCP, and SDK source paths that the returned Decimal value is passed through without a visible accumulation or scaling transformation.

However, we do not want to infer a monetary contract from observed values or implementation behavior. We therefore need authoritative clarification of the following points:

  1. Series semantics

Does each CapitalFlowLine.inflow returned by QuoteContext.capital_flow(symbol) represent the net inflow for that individual minute, rather than a cumulative intraday value?

Does this same semantic contract apply to the value exposed through the official SDK, CLI, and Hosted MCP capital_flow tool?

  1. Monetary unit and scale

What is the exact monetary unit of CapitalFlowLine.inflow?

For example, is the returned Decimal already expressed in the major currency unit, or is there an implicit minor-unit or other numeric scale?

Please specify any required multiplier or divisor.

  1. Currency

Is capital_flow denominated in the security's quote currency?

Specifically, would:

AAPL.US capital flow be denominated in USD; and
700.HK capital flow be denominated in HKD?

Is this rule guaranteed for all supported securities/markets?

  1. capital_distribution compatibility

For the same symbol, do the monetary values returned by capital_flow and capital_distribution use exactly the same:

monetary unit,
numeric scale, and
currency?

  1. turnover dimensional compatibility

Does the turnover field returned by the official quote and candlestick interfaces use the same monetary unit, scale, and currency contract as capital_flow.inflow?

In particular, is the following expression dimensionally valid without any additional unit or currency conversion?

sum(CapitalFlowLine.inflow) / turnover

  1. Hidden transformations

Is there any implicit multiplier, divisor, denomination conversion, currency conversion, or other numeric transformation between the underlying provider value and the value exposed by:

QuoteContext.capital_flow → official SDK → official CLI / Hosted MCP?

If possible, please provide or identify the authoritative and versioned documentation, schema, source contract, or technical specification that guarantees these answers.

If no published specification currently exists, a written confirmation from the Longport technical team stating the applicable contract and the affected API/SDK versions would also be very helpful.

This request contains no access token, refresh token, account identifier, cookie, Authorization header, or other credential.

Thank you.

Lingua principale
TypeScript
Stelle
61
Fork
30
Merge medio
7h 45m
PR unite (30g)
17

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di longbridge/developers

Tutte le issue di longbridge/developers

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.