Clarify dated-contract support for premiumIndexKlines (USD-M and COIN-M)

Chiusa
  • Qualcosa non va?
#585 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
56/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, backend-api-design, documentation

Direzione di ricerca

Start with the USD-M and COIN-M premium index kline endpoint documentation and the generated Python premium_index_kline_data methods named in the issue. Compare the documented symbol and contract rules with the reported public responses, then determine the official behavior with maintainers. Done when both endpoint pages clearly state dated-contract support or exclusion, expected responses and any migration guidance.

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

Descrizione

Question

Does GET /fapi/v1/premiumIndexKlines or GET /dapi/v1/premiumIndexKlines
support dated USD-M / COIN-M futures, including CURRENT_QUARTER and NEXT_QUARTER?
Please clarify the supported contract types in the official endpoint documentation.

The current USD-M market-data page,
COIN-M market-data page
and generated Python methods describe symbol/interval and optional time/limit
parameters without a perpetual/dated applicability rule. Section C.3 of the
CM/UM integration notice
lists both premiumIndexKlines paths among endpoints accepting CM/UM symbols;
it does not distinguish perpetual and dated contract eligibility.

Public, unsigned reproduction

Observed on 2026-10-28, 15:30:04–15:30:10 UTC, using direct HTTP GET to the
native host with symbol=<native symbol>&interval=1m&limit=2. No key, account,
order endpoint or authenticated request is involved.

Host / path Native symbols Result
fapi.binance.com /fapi/v1/premiumIndexKlines BTCUSDT_261225, BTCUSDT_270326, ETHUSDT_261225, ETHUSDT_270326 Each HTTP 400, code -1121, Invalid symbol
dapi.binance.com /dapi/v1/premiumIndexKlines BTCUSD_261225, BTCUSD_270326, ETHUSD_261225, ETHUSD_270326 Each HTTP 400, code -1121, Invalid symbol
fapi.binance.com /fapi/v1/premiumIndexKlines BTCUSDT, ETHUSDT Each HTTP 200, two kline rows
dapi.binance.com /dapi/v1/premiumIndexKlines BTCUSD_PERP, ETHUSD_PERP Each HTTP 200, two kline rows

Complete error response for the dated premium queries:

{"code":-1121,"msg":"Invalid symbol."}

Examples:

curl 'https://fapi.binance.com/fapi/v1/premiumIndexKlines?symbol=BTCUSDT_261225&interval=1m&limit=2'
curl 'https://dapi.binance.com/dapi/v1/premiumIndexKlines?symbol=BTCUSD_261225&interval=1m&limit=2'

For these two dated symbols, adding
startTime=1793201280000&endTime=1793201399999 (15:28:00–15:29:59.999 UTC,
two already closed minutes) also returned 400/-1121.

A subsequent fresh native exchangeInfo check found all eight dated symbols
with their exact native symbols and CURRENT_QUARTER/NEXT_QUARTER identities,
all TRADING (status for USD-M, contractStatus for COIN-M). These observations
do not establish that the premium endpoint permanently excludes dated contracts.

The current generated Python premium_index_kline_data methods use the same
native paths, with no additional pair or contractType parameter. The direct
HTTP result above does not depend on SDK response-model decoding.

Requested clarification

  1. If premiumIndexKlines is intentionally perpetual-only, please document that
    separately for USD-M and COIN-M, including migration behavior and the expected
    response for a listed dated symbol.
  2. If dated contracts are supported, what exact symbol/parameters, path and time
    availability rules should a client use? Please provide a successful dated
    example or identify a service defect.
  3. Does any published premium series have pair/shared scope rather than native
    dated-product scope? If so, please identify its official identity and semantics.
    We cannot assign a perpetual premium, mark-price bar, index-price bar or a
    locally computed basis to a dated-product premium series without that contract.

We are preserving these failures as unknown coverage until an official rule is
available. A documented exclusion and a supported dated query require different
client behavior; an Invalid symbol response alone cannot distinguish them.

Environment

Public production fapi/dapi hosts, direct unsigned HTTP GET. The reproduction does not use the Python SDK and is independent of its response models. No API key, signature, cookie, account, or trading endpoint is used. The curl examples above can reproduce the request without installing a connector.

Lingua principale
Python
Stelle
3k
Fork
712
Merge medio
1g 13h
PR unite (30g)
9

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 binance/binance-connector-python

Tutte le issue di binance/binance-connector-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.