BROKER API · TECHNICAL REFERENCE
Longbridge API Technical Reference
Technical reference for Longbridge market data, authentication, REST, WebSocket, trading, account APIs, environments, SDKs, and integration considerations.
Quick answer. Longbridge should be integrated as a capability-scoped provider adapter. Confirm market, account, product, environment, permissions, native symbols, rate limits, and order semantics from the official documentation before enabling execution.
Overview
Multi-market brokerage API coverage depends on account and product.
API surface
| Area | Current reference |
|---|---|
| Authentication | Provider-specific credentials and session lifecycle; see official docs. |
| REST API | REST and streaming interfaces require account and market entitlements. |
| WebSocket / streaming | Confirm channels, sequence numbers, reconnect rules, and entitlement requirements. |
| FIX | Not verified in this release; do not infer FIX availability from REST or WebSocket support. |
| Paper / demo / testnet | Confirm the environment and account scope in the provider documentation. |
| Rust SDK | Not verified in this release; use provider documentation. |
| Last verified | 2026-09-28; production capability review pending. |
Integration considerations
- Keep the provider-native symbol and order ID alongside canonical identifiers.
- Model account, environment, permissions, and entitlements separately.
- Use REST snapshots with streaming events for reconciliation.
- Persist an Unknown state when an order response is ambiguous.
Sources
Last verified: 2026-09-28. Provider capabilities can change by region, account, product, environment, and entitlement; verify the linked official documentation before production use.