Free Options Data
with Python用 Python 获取
免费期权数据

TL;DR核心摘要

The practical answer is to begin with one narrow, repeatable request: one underlying, one expiry, and a documented set of fields. Save the response before transforming it, normalize the contract identity and quote timestamp, then reject rows that fail basic market-data checks. Only after that workflow is stable should you add more expiries, symbols, or scheduled collection.

更实用的做法是从一个范围明确、可以重复执行的请求开始：一个标的、一个到期日，以及一组有文档说明的字段。先保存响应，再规范化合约身份与报价时间戳，并排除未通过基本行情检查的记录。只有这套流程稳定后，才适合增加更多到期日、标的或定时采集任务。

This guide is for developers building research notebooks, option screeners, teaching examples, or data-ingestion prototypes. It is not a recommendation to trade an option, and it does not treat a free quote as complete evidence for execution or historical performance.

本指南面向构建研究 Notebook、期权筛选器、教学示例或数据采集原型的开发者，不构成期权交易建议，也不会把一条免费报价视为成交或历史绩效的完整证据。

Choose a free options data source for Python选择适用于 Python 的免费期权数据源

Start with the dataset—not the library. A current chain screener needs bid, ask, volume, open interest, IV, strike, expiry, and contract side. Backtesting also needs historical chain snapshots, which are much harder to find on a free plan.

先确定所需的数据集，而不是先选择库。筛选当前期权链需要买价、卖价、成交量、持仓量、隐含波动率、行权价、到期日以及看涨或看跌类型；回测还需要历史期权链快照，而这类数据通过免费套餐更难获得。

Define the job before comparing sources. A notebook that ranks contracts by spread needs current bid and ask sizes; an implied-volatility study needs the option price, synchronized underlying price, valuation time, rate, dividend assumption, and calculation method. If you only need to learn DataFrame operations, a documented sample file may be more stable than an undocumented public endpoint.

比较数据源之前，先明确任务。按价差筛选合约的 Notebook 需要当前买卖价和挂单量；研究隐含波动率则需要期权价格、同步的标的价格、估值时间、利率、股息假设和计算方法。如果目的只是学习 DataFrame 操作，一份有说明的样例文件往往比未经说明的公开接口更稳定。

Treat “free” as an access condition, not a quality grade. Record the source, retrieval time, advertised delay, request parameters, terms of use, and the fields actually returned. That small provenance record lets you explain why two runs produced different chains.

“免费”描述的是访问条件，并不代表数据质量等级。应记录数据来源、获取时间、标称延迟、请求参数、使用条款以及实际返回字段。保留这些基本来源信息，才能解释两次运行为什么得到不同的期权链。

Keep adjacent search intents separate. If the main decision is which endpoint or provider model to use, continue with the free options data API selection guide. For a file-first workflow, use the free options data CSV guide to define columns, encoding, and import checks before writing Python transformations.

相邻搜索意图应保持区分。如果核心问题是选择哪种端点或供应商模式，可继续阅读免费期权数据 API 选型指南；如果采用文件优先的工作流，则可参考免费期权数据 CSV 指南，先确定字段、编码与导入检查，再编写 Python 转换逻辑。

Quote fields also need market context. Option chains present buying and selling interest through bid and ask values, and the spread matters alongside either price. That is why a source returning only a last price is inadequate for many screening and execution studies.

报价字段还需要结合市场背景理解。期权链通过买价和卖价展示市场两侧的交易意愿，价差与两侧价格本身同样重要。因此，只返回最新成交价的数据源并不足以支持许多筛选和成交研究。

Python example: fetch an option chain into pandasPython 示例：获取期权链数据并读入 pandas

A provider-neutral pattern uses requests for transport and pandas for normalization. Replace the endpoint, authentication method, response path, pagination rules, and field names with those in your provider’s documentation. The example intentionally stops at ingestion and validation; it does not generate a trading recommendation.

一种与数据供应商无关的通用做法是使用 requests 发起 HTTP 请求，再通过 pandas 规范数据结构。请根据所选供应商的文档替换 API 端点、认证方式、响应路径、分页规则和字段名。这个示例只演示获取与验证数据，并不生成交易建议。

import os
import requests
import pandas as pd

url = "https://api.example.com/v1/options/chain"
params = {
    "underlying": "AAPL",
    "expiry": "2026-09-18",
    "apikey": os.environ["OPTIONS_API_KEY"],
}
response = requests.get(url, params=params, timeout=20)
response.raise_for_status()

rows = response.json()["contracts"]
df = pd.DataFrame(rows)
df["quote_time"] = pd.to_datetime(df["quote_time"], utc=True)
df["expiry"] = pd.to_datetime(df["expiry"])
key = ["expiry", "strike", "side"]
df = df.sort_values("quote_time").drop_duplicates(key, keep="last")
print(df[key + ["bid", "ask", "iv", "delta", "open_interest"]].head())

Real APIs often return nested JSON rather than a flat contracts array. Inspect one raw response before writing transformation code, then use a documented record path or pandas.json_normalize when contracts are nested under expiries or option sides. Keep the raw payload unchanged so you can revisit fields that were not included in the first DataFrame.

真实 API 经常返回嵌套 JSON，而不是平铺的 contracts 数组。编写转换逻辑前，应先检查一份原始响应；如果合约嵌套在不同到期日或期权类型之下，可使用明确的记录路径或 pandas.json_normalize 展开。原始响应应保持不变，以便以后重新提取首次 DataFrame 未保留的字段。

For repeated collection, separate immutable raw files from normalized tables. Partition by retrieval date and underlying, save the provider request ID when available, and write a small manifest containing schema version, row count, minimum and maximum quote time, and validation status. This makes failed or incomplete downloads visible before they enter analysis.

如果需要持续采集，应把不可变的原始文件与规范化表分开。可按获取日期和标的分区，在供应商提供请求 ID 时一并保存，并生成包含数据结构版本、行数、最早和最晚报价时间及验证状态的小型清单。这样可以在数据进入分析前发现失败或不完整的下载。

For a scheduled collector, make each run idempotent: the same request window should produce the same partition key, while a changed payload creates a new version rather than silently overwriting history. Add bounded retries for timeouts and temporary server errors, but do not retry invalid credentials, malformed parameters, or permission failures as if they were transient.

定时采集任务应具备幂等性：相同请求区间应生成相同分区键；响应内容变化时应创建新版本，而不是静默覆盖历史。遇到超时或临时服务器错误时可以有限重试，但无效凭证、错误参数或权限失败不应被当作临时问题反复请求。

Validate free options data before analysis使用免费期权数据分析前，先做好验证

Turn these checks into assertions or a machine-readable validation report. At minimum, report duplicate contract keys, stale timestamps, negative prices, bid-above-ask rows, missing expiries, unexpected currencies, and the percentage of contracts without volume, open interest, IV, or Greeks. Fail the pipeline on broken identity or timestamps; warn separately about optional analytics that the source never promised.

应把这些检查写成断言或机器可读的验证报告。最低限度需要报告重复合约键、陈旧时间戳、负价格、买价高于卖价、缺失到期日、异常币种，以及缺少成交量、持仓量、隐含波动率或希腊值的合约比例。合约身份或时间戳错误应使管道直接失败；供应商未承诺提供的可选指标则可以单独警告。

Contract identity deserves special treatment. Corporate actions can create adjusted contracts whose deliverables differ from a standard 100-share contract. Preserve the provider contract ID, multiplier, deliverable, and adjustment indicator instead of reconstructing identity from strike and expiry alone.

合约身份需要单独重视。公司行动可能产生交割物不同于标准 100 股合约的调整期权。因此，应保留供应商合约 ID、乘数、交割物和调整标记，而不是只根据行权价与到期日重建合约身份。

If the goal is strategy simulation rather than current-chain analysis, move to the free options data for backtesting guide. That workflow needs historical point-in-time snapshots, contract lifecycle handling, realistic fill assumptions, and a stricter evidence standard than a current Python chain fetch.

如果目标是策略模拟，而不是分析当前期权链，应继续阅读免费期权回测数据指南。回测需要历史时点快照、合约生命周期处理、现实的成交假设，以及比当前 Python 期权链请求更严格的证据标准。

Use QVeris for provider-flexible options data access借助 QVeris 灵活接入多家期权数据服务商

Use the documented discover → inspect → call sequence. For this workflow, start by inspecting the Realtime Options tool in QVeris, including its symbol, contract, data-format, and optional Greeks parameters. Then review the Alpha Vantage provider profile before deciding whether it fits the required market coverage and workflow.

可以采用文档说明的“发现 → 检查 → 调用”流程。对于当前工作流，可先检查 QVeris 中的 Realtime Options 工具，核对股票代码、合约、数据格式以及可选希腊值参数；随后查看 Alpha Vantage Provider 详情，再判断其市场覆盖与工作流是否符合需求。

Python applications can implement that workflow with the QVeris Python SDK. Begin with a narrow discovery query such as “US equity option chain with bid, ask, open interest, and quote timestamp,” inspect the returned schema, and test one underlying and expiry. If you want to evaluate the interaction before adding code, run the same narrow task in the QVeris Playground.

Python 应用可以通过 QVeris Python SDK 实现这套流程。可以先使用“包含买价、卖价、持仓量和报价时间戳的美股期权链”这类范围明确的发现请求，检查返回的数据结构，再测试一个标的与到期日。如果希望在编写代码前评估交互流程，也可以在 QVeris Playground 中运行同样的窄范围任务。

• Discover options-data capabilities and inspect their inputs before calling them.
• Keep application code focused on underlyings, expiries, strikes, and normalized outputs.
• Use a direct provider integration instead when you need an exchange-specific feed, contract, or operational control that the inspected capability does not expose.

• 查找可用的期权数据能力，并在调用前核对输入参数。
• 让应用代码只需处理标的资产、到期日、行权价以及标准化后的输出。
• 如果需要检查后发现能力未提供某项交易所专用行情、合同条款或运营控制，应继续采用供应商直接集成。

FAQ常见问题

References and next steps参考资料与下一步

Alpha Vantage options documentation

Alpha Vantage 期权文档