mirror of
https://github.com/longbridge/developers.git
synced 2026-09-19 03:34:09 +08:00
hold-baby
b874d3c582
## Merge Verdict **[APPROVE]** — Docs-only copy change; auth code TTL updated from 5 to 10 minutes, consistently applied across all three locales. > 3 files · +9 / -9 · `docs/en` `docs/zh-CN` `docs/zh-HK` --- ## Change Summary - Updates the AI Agent auth code TTL from **5 minutes** to **10 minutes** on the `agent-auth` page. - All 3 mentions per file are covered: the intro statement, the Security bullet (`10-minute TTL`), and the "code has expired" troubleshooting note. - Applied identically in `en` / `zh-CN` / `zh-HK`, satisfying the repo's trilingual sync rule. --- ## Risk Analysis | Risk | Level | Mitigation | |------|-------|------------| | Docs drift from backend TTL | 🟡 | Requires the server-side auth code TTL to actually be 10 minutes; otherwise users will hit an expiry earlier than documented | | Missed occurrences | ✅ | `grep` over `docs/` confirms no remaining "5 minutes / 5 分钟 / 5 分鐘" reference to the auth code TTL | | Locale divergence | ✅ | Same 3 edits in all three locale files, verified line by line | --- ## Design Decisions - **Terminology kept intact**: only the number changed; wording, bold markers and links are untouched, so translation parity is preserved. - **Device-flow polling left alone**: `docs/{lang}/skill/install/index.md` mentions "~5 minutes" for the `auth login` device-code polling window — a different mechanism from the one-time auth code, correctly not modified. --- ## Code Concerns 1. **[需判断]** Docs change assumes the backend TTL is already 10 minutes (`docs/en/docs/agent-auth.md:37`) Docs are not the source of truth here; confirm the auth service has shipped the 10-minute TTL before merging, otherwise the page over-promises. --- ## Verification Status ✅ Markdown-only change · ✅ Trilingual sync verified · 📋 To verify: backend auth code TTL is actually 10 minutes Co-authored-by: 袁昌瑞 <changrui.yuan@longbridge-inc.com>
Longbridge Developers
Longbridge Developers is the official developer platform for Longbridge — providing programmatic access to real-time market data, trading, account management, and AI integrations across HK, US, and CN markets.
Repository structure
/
├── docs/ # Site content and VitePress config
│ ├── .vitepress/ # Theme, components, markdown plugins, locale configs
│ ├── en/ # English content (root locale)
│ ├── zh-CN/ # Simplified Chinese content
│ └── zh-HK/ # Traditional Chinese content
├── openapi/ # Submodule: OpenAPI spec + SDK source (openapi, Python, Rust, etc.)
├── openapi-go/ # Submodule: Go SDK
├── longbridge-terminal/ # Submodule: CLI binary source (longbridge)
├── skills/longbridge/ # AI Skill — knowledge base for AI agents
├── scripts/ # Build scripts (llms.txt generation, markdown normalization)
├── openapi.yaml # Canonical API specification (source of truth for API Reference)
└── CONTRIBUTING.md # Contribution guidelines for AI agents and humans
What you can build
- Automated trading strategies and order management
- Real-time quote dashboards and data pipelines
- Portfolio trackers and risk monitoring tools
- AI agents with live market data and trading capabilities
Access methods
| Method | Best for |
|---|---|
| SDK | Python, Rust, Node.js, Go, Java, C++ apps |
| HTTP / WebSocket API | Any language, custom integrations |
CLI (longbridge) |
Terminal workflows, scripting, AI tool-calling |
| MCP | ChatGPT Apps and AI assistants (Cursor, Claude, etc.) |
| Skill | Give any AI direct knowledge of Longbridge APIs |
Quick start
1. Open a Longbridge account
Download the Longbridge App and complete account onboarding.
2. Enable OpenAPI access
Log in to open.longbridge.com, complete developer verification, and obtain your API token.
3. Choose your integration
CLI — fastest way to get started:
brew install --cask longbridge/tap/longbridge-terminal
longbridge auth login
longbridge quote TSLA.US NVDA.US 700.HK
Python SDK:
pip install longbridge
MCP for AI assistants — in ChatGPT web, desktop, or mobile, open the Longbridge ChatGPT App or search longbridge in Apps, authorize, then use @longbridge in the message box.
For other MCP clients, add Longbridge as a remote MCP server:
{
"mcpServers": {
"longbridge": {
"url": "https://mcp.longbridge.com"
}
}
}
AI Skill — give your AI full knowledge of Longbridge APIs:
npx skills add longbridge/developers -g -y
Market coverage
| Market | Instruments |
|---|---|
| Hong Kong | Equities, ETFs, Warrants, CBBCs, Hang Seng Index |
| United States | Stocks, ETFs, OPRA Options, Nasdaq Index |
| China A-share | Stocks, ETFs, Index |
Documentation
- Getting Started — https://open.longbridge.com/docs/getting-started
- API Reference — https://open.longbridge.com/docs/api
- SDK Reference — https://open.longbridge.com/sdk
- CLI Reference — https://open.longbridge.com/docs/cli
- MCP Setup — https://open.longbridge.com/docs/mcp
- LLM / AI Integration — https://open.longbridge.com/docs/llm
- Changelog — https://open.longbridge.com/docs/changelog
LLM-friendly docs
All documentation pages are available as Markdown by appending .md to any URL:
https://open.longbridge.com/docs/getting-started.md
https://open.longbridge.com/docs/quote/pull/static.md
A machine-readable index is available at:
https://open.longbridge.com/llms.txt
Pricing
OpenAPI access is free for Longbridge Integrated Account holders. No additional fees for activating or using the API. Standard brokerage transaction fees apply to trades.
Contributing
Local development setup
git clone --recurse-submodules https://github.com/longbridge/developers.git
cd developers
bun install
bun run dev
If you already cloned without --recurse-submodules:
git submodule update --init --recursive
bun run dev
The dev server starts at http://localhost:5173 and connects to the canary API. Use bun run dev:prod to connect to the production API instead.
See CONTRIBUTING.md for full contribution guidelines.