Longbridge OpenAPI SDK

Longbridge OpenAPI provides programmatic quote trading interfaces for investors with research and development capabilities and assists them to build trading or quote strategy analysis tools based on their own investment strategies. The functions fall into the following categories:

• Trading - Create, amend, cancel orders, query today’s/past orders and transaction details, etc.
• Quotes - Real-time quotes, acquisition of historical quotes, etc.
• Portfolio - Real-time query of the account assets, positions, funds
• Real-time subscription - Provides real-time quotes and push notifications for order status changes

This repo contains the following main components:

Context Types

Quickstart

Pick a language SDK from the table above and follow its README for install and first request. Full reference docs: https://longbridge.github.io/openapi

SDK Documentation

https://longbridge.github.io/openapi

Troubleshooting

• Environment variables not taking effect
  • macOS/Linux: export ... only affects the current shell session.
  • Windows: setx ... requires opening a new terminal/session to take effect.
• Authentication errors (401/403)
  • Verify LONGBRIDGE_APP_KEY, LONGBRIDGE_APP_SECRET, LONGBRIDGE_ACCESS_TOKEN are correct and not expired.
  • Ensure your OpenAPI app has the required permissions.
• Network / connection errors
  • Check firewall/proxy rules for HTTPS/WSS.
  • If you use a custom endpoint, set LONGBRIDGE_HTTP_URL, LONGBRIDGE_QUOTE_WS_URL, LONGBRIDGE_TRADE_WS_URL.
• Quote subscription exits immediately
  • Keep the process running (event loop / sleep / blocking receive loop), otherwise you will not see push events.
• Debugging
  • Enable logs via LONGBRIDGE_LOG_PATH.
  • If quotes connect but look empty, keep LONGBRIDGE_PRINT_QUOTE_PACKAGES=true to confirm opened quote packages.
• Paper trading
  • If your account is a paper trading (simulation) account and you want to place orders, set LONGBRIDGE_PAPERTRADING=true. When enabled, all API calls target the paper trading environment and the server validates the token — if the token belongs to a real-money account the server returns an error. When false (the default) the server imposes no restrictions.

Minimal Verification

If you're not sure whether your environment / credentials are correct, start with the built-in HTTP client examples.

• Python:

  python examples/python/http_client.py
  

• Node.js:

  node examples/nodejs/http_client.js
  

• Rust:

  cargo run --manifest-path examples/rust/Cargo.toml -p http_client
  

• Java (from the example module directory):

  cd examples/java/http_client
  mvn -q -DskipTests package
  mvn -q -DskipTests exec:java
  

• C/C++:

  • Use the sources in examples/c/http_client/main.c and examples/cpp/http_client/main.cpp.
  • Build instructions depend on your toolchain; see the corresponding language SDK README.

Expected results:

• If credentials are valid and network is reachable, the HTTP call returns JSON.
• If it returns 401/403, check your LONGBRIDGE_APP_KEY, LONGBRIDGE_APP_SECRET, LONGBRIDGE_ACCESS_TOKEN.
• If it times out / cannot connect, check proxy/firewall and your endpoint env vars.

Resources

• Longbridge OpenAPI
• Longbridge OpenAPI Docs

License

Licensed under either of

• Apache License, Version 2.0,(LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT) at your option.