Clarify dated-contract support for premiumIndexKlines (USD-M and COIN-M)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 56/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
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
- 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. - 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. - 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 小时
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
binance/binance-connector-python 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 55/100
binance/binance-connector-python#587 · 1 条评论 ·
维护者通常 1 天内回复
-
USDⓈ-M exchangeInfo：请明确 POSITION_RISK_CONTROL / positionControlSide 的语义与枚举可能已有人在做 @Tyagiquamar 于 2 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 15/100
binance/binance-connector-python#575 · 2 条评论 ·
维护者通常 1 天内回复
-
[Bug] Response models declare numeric fields as strict `str`, causing silent fallback of `.data()` to raw dict (simple-earn & staking)可能已有人在做 @Tyagiquamar 于 48 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 68/100
binance/binance-connector-python#553 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 20/100
binance/binance-connector-python#498 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 30/100
binance/binance-connector-python#464 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
查看 binance/binance-connector-python 的全部 Issue
相似的 Issue
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 77/100
githubnext/gh-aw-workshop#5367 ·
维护者通常 3 天内回复
-
Create Noise Latents ignores randomize_seed and produces the same noise every run可能已有人在做 @griptapeops 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
griptape-ai/griptape-nodes-library-diffusers#127 ·
维护者通常 1 天内回复
-
Jenkins capacity report: metrics history is lost when archiving a month fails可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
adoptium/infrastructure#4568 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
huggingface/deep-rl-class#723 ·
-
premises-missing
难度 2/5 1-3 小时 新手友好度 78/100
WingedGuardian/GENesis-AGI#3928 ·
维护者通常 1 天内回复