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

Cerrado
  • ¿Algo no está bien?
#585 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
56/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend-api-design, documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
3k
Forks
712
Merge medio
1 d 13 h
PR fusionados (30 d)
9

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de binance/binance-connector-python

Todos los issues de binance/binance-connector-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.