Skip to content
Longport WhaleLongport Whale
Guides

Integration Options

Choose by UI delivery, caller, and authorization subject

First decide whether Whale should supply the graphical UI. Then decide whether the caller represents the Broker institution or one Client.

Comparison

Product Caller Authorization subject Form Best fit Status
WhaleAppSDK Broker App team Client iOS / Android / WebTrade graphical SDK Integrate a complete securities UI in Broker App, website, or web container Available
WhaleCoreSDK + TradingAPI Broker App Client iOS / Android / Web data SDK + HTTP API Broker App implements the complete securities UI iOS / Android available; WebAssembly in development
BrokerAPI Broker Server / self-built administration backend Broker HTTPS API Server-to-Server integration or a self-built administration system Available
OpenAPI ↗ A Broker’s Developers and AI apps Client Open API / SDK / MCP Algorithmic trading, quantitative analysis, and AI access to Client-authorized accounts and market data Available

Ready-made or custom UI

  • Ready-made UI: choose WhaleAppSDK. iOS and Android provide native UI; WebTrade can be deployed on a standalone domain for direct user access or embedded in a Broker’s website via iframe.
  • Implement the complete securities UI: use WhaleCoreSDK + TradingAPI. WhaleCoreSDK supplies market subscriptions, WebSocket connectivity, request signing, token renewal, and other client foundations; TradingAPI supplies account, asset, trading, and related HTTP capabilities.
flowchart TD
    A[Broker builds a Client trading experience] --> B{Use Whale's complete UI?}
    B -- Yes --> C{Target platform}
    C -- iOS --> D[WhaleAppSDK for iOS]
    C -- Android --> E[WhaleAppSDK for Android]
    C -- Web --> F[WebTrade]
    B -- No, implement all UI --> G[WhaleCoreSDK + TradingAPI]
    G --> H[iOS / Android WhaleCoreSDK]
    G --> I[WebAssembly in development]

Authorization boundaries

  • Broker-scoped authorization: Server-to-Server integrations and self-built administration systems use BrokerAPI; requests originate from a Broker-controlled server.
  • Client-scoped authorization: WhaleAppSDK, including WebTrade, WhaleCoreSDK, TradingAPI, and OpenAPI access private data as one Client.
  • Broker Developers vs. Developers: a Broker Developer builds the Broker product on the Broker’s behalf; a Developer is a Broker Client building on OpenAPI. The two never share credentials or authorization scope.
Note

WhaleCoreSDK has no graphical UI and does not replace TradingAPI. A Broker App implementing the complete securities UI normally combines WhaleCoreSDK connection and session foundations with TradingAPI HTTP business endpoints.

Whale Docs