webull-events
Explain and plan Webull Thailand real-time market-data MQTT subscriptions and gRPC trade-event subscriptions. Use for streaming architecture, topics, lifecycle, or event handling; do not pretend the shared HTTP CLI maintains persistent sessions.
nutdnuy · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add nutdnuy/webull-openapi-AI-Plugin --skill webull-events技能说明
name: webull-events description: Explain and plan Webull Thailand real-time market-data MQTT subscriptions and gRPC trade-event subscriptions. Use for streaming architecture, topics, lifecycle, or event handling; do not pretend the shared HTTP CLI maintains persistent sessions.
Webull events and streaming
Read references/endpoints.json, follow each HTTP control entry's schema_ref into references/openapi.json, and read references/authentication.md for request shapes and credentials. Consult the official Webull Open API reference, Market Data API FAQ, and Trading API Getting Started.
First-use onboarding
Before explaining or starting a streaming workflow, check for WEBULL_APP_KEY and WEBULL_APP_SECRET in the secure environment. If the API Key is missing, ask the user to configure it securely and stop. Never request or echo secrets in chat.
Supported streaming interfaces
POST /openapi/market-data/streaming/subscribe— MQTT market-data subscription operation; official reference index.POST /openapi/market-data/streaming/unsubscribe— MQTT market-data unsubscribe operation; official docs.subscribeTradeEvents— conceptual gRPC trade-event subscription (the catalog entry hastransport: grpcand no HTTP method/path); official getting-started docs.
Workflow
-
Read the catalog entry for the MQTT subscribe/unsubscribe request shape and the auth reference for connection prerequisites. Treat subscribe/unsubscribe as streaming lifecycle operations, not ordinary one-shot data reads.
-
Explain connection identity, topic/session lifecycle, heartbeat/reconnect behavior, permissions, and documented limits from the official docs. Do not promise delivery or silently restore subscriptions after disconnect unless the client explicitly implements that behavior.
-
The shared CLI is an HTTP request client. It does not open or hold persistent MQTT or gRPC sessions. You may use it only for a documented one-shot control request, with catalog-shaped placeholders:
python scripts/webull_api.py request --method POST --path /openapi/market-data/streaming/subscribe --body-file ./subscribe.json --allow-write --write-confirmation STREAMING python scripts/webull_api.py request --method POST --path /openapi/market-data/streaming/unsubscribe --body-file ./unsubscribe.json --allow-write --write-confirmation STREAMING -
Do not claim that the CLI received live binary protobuf/MQTT messages or gRPC order events. Recommend an official Webull SDK or a purpose-built persistent client for those sessions, with secrets kept outside logs and source control. Do not invent an HTTP path for
subscribeTradeEvents.