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

クローズ
  • 何か問題がありますか？
#585 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
56/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
api, backend-api-design, documentation

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Python
スター
3k
フォーク
712
平均マージ
1日 13時間
マージ済み PR（30日）
9

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

binance/binance-connector-python のほかの issue

binance/binance-connector-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。