canonical: https://jentic.com/apis/interactivebrokers.com/interactivebrokers # Interactivebrokers IBKR 3rd Party Web API The Interactive Brokers 3rd Party Web API exposes a subset of IBKR brokerage operations to approved third-party platforms, covering account information, positions, balances, orders, and trade history across IBKR's global markets. The 16 operations are session-authenticated using the cookieAuth scheme, where a successful login returns a session cookie that subsequent calls reuse. The API targets advisor and white-label integrations rather than retail self-service, and it sits alongside IBKR's TWS API and Client Portal API as the structured route for partner applications. ## For AI agents Read account positions, balances, orders, and trade history from Interactive Brokers accounts via the partner Web API. ## Scope Does not handle real-time market data streaming, retail account opening, custody for non-IBKR brokerages, or research data - use for partner-approved IBKR account, position, order, and trade operations only. ## Capabilities - List accounts the authenticated user can act on and read per-account summary data - Retrieve open positions and aggregated portfolio balances for a given IBKR account - Pull historical orders and executed trades for reconciliation and reporting - Submit and cancel orders against IBKR's global execution venues from approved partner integrations - Authenticate via cookie-based session and refresh the session as needed - Read instrument and contract metadata required to construct order tickets ## Use cases ### Wealth Platform Account Aggregation Fintech platforms that aggregate brokerage accounts read positions and balances from IBKR through this Web API to render unified portfolios. The session cookie issued at login authorises subsequent reads, and the platform refreshes data on a scheduled cadence rather than per page view. Onboarding requires IBKR partner approval but the data flow is straightforward once credentials are in place. Example prompt: Fetch all open positions for IBKR account U7891234 and emit symbol, quantity, and unrealised P&L per row ### Advisor Trade Reconciliation Registered investment advisors using IBKR as their custodian reconcile end-of-day trades against their portfolio management system by pulling the day's order and trade history. The Web API returns the executed orders with fills, prices, and timestamps in a single structured response. Daily reconciliation that previously involved CSV export and manual matching becomes a scheduled job. Example prompt: Retrieve all executions on 2026-06-09 for account U7891234 and emit one row per fill with symbol, quantity, price, and venue ### Algorithmic Order Routing Quantitative trading partners route orders into IBKR's smart router via the Web API, monitoring fills and adjusting in response. Order submission and cancellation share the same session cookie used for read calls, simplifying token management compared with OAuth-style flows. The API is appropriate where partner-level approval is in place and the latency profile (HTTPS REST) fits the strategy. Example prompt: Submit a limit buy order for 50 shares of MSFT at $410.00 day-only via IBKR and store the returned orderId ### Agent-Driven Portfolio Monitoring An AI agent monitors a client's IBKR account on demand: when the client asks 'what's my exposure to tech?' the agent calls the positions endpoint, classifies holdings by sector, and answers in natural language. Jentic stores the IBKR session credentials in your Jentic One instance so the agent never sees the underlying password. This collapses what would normally be a portal login plus manual classification into a one-shot conversation. Example prompt: Pull positions for IBKR account U7891234, group by GICS sector, and report the dollar exposure to Information Technology ## Key resources - **Accounts** — List accounts and read account summary metadata - **Positions** — Retrieve open positions and per-account portfolio breakdowns - **Orders** — Submit, cancel, and list orders across IBKR's execution venues - **Trades** — Read executed trades and fills for reconciliation - **Session** — Cookie-based authentication and session lifecycle ## Why Jentic - **Setup:** Wiring the IBKR 3rd Party Web API by hand means managing its portal session credential, holding the partner approval token, and tracking the `/tradingapi/v1` base path. Through Jentic you install once, import the IBKR 3rd Party Web API from the API Directory, store the session credentials once, and your agent calls it. - **Permission scoping:** IBKR carries the target in the request body under a partner-approved session, so limit the agent to the operations it needs, such as listing positions or reading orders. You choose the operations it may call, so order placement is not included unless you add it. - **Credential handling:** Your IBKR session credentials and partner approval token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list IBKR positions', and Jentic returns the matching IBKR Web API operation with its input schema so the agent calls the right endpoint without parsing the partner docs. ## Related APIs - **Alpaca Trading API** — REST-first US equities and crypto broker versus the IBKR partner Web API - **Tradier API** — US equity and options broker API versus IBKR's global multi-asset coverage - **Polygon.io API** — Market data feeds that pair with brokerage execution APIs - **Finnhub API** — Fundamentals and news data that complements brokerage execution ## FAQ ### What authentication does the IBKR 3rd Party Web API use? It uses cookie-based session authentication (cookieAuth in the spec). A successful login establishes a session cookie that the client must replay on every subsequent call. Through Jentic, the session credentials are held in your Jentic One instance and the agent receives only the active session reference, never the underlying password. ### Can I submit orders through this API? Yes. The API includes order submission and cancellation paths alongside the read-only account, position, and trade endpoints. Order placement requires that your firm has been approved as an IBKR third-party partner - this is not a retail self-service API. ### What are the rate limits for the IBKR 3rd Party Web API? The OpenAPI spec does not state numeric limits. Interactive Brokers applies request pacing on its trading APIs and rejects bursty traffic with HTTP 429 or session lockouts; design retries with exponential backoff and respect the documented partner usage agreement. ### How do I read open positions for an account through Jentic? Search Jentic for 'list IBKR positions'. The SDK returns the positions GET operation with the accountId path/query parameter. Run pip install jentic, await client.search('list IBKR positions'), then await client.execute(...) with the account identifier. ### Is the IBKR 3rd Party Web API free? Access is gated by IBKR partner approval and tied to the underlying brokerage relationship. There is no separate per-call fee published in the spec - costs flow through trading commissions, market data subscriptions, and the partner agreement with Interactive Brokers. ### Does this API stream market data? No. The 3rd Party Web API covers account, position, order, and trade operations only. For real-time quotes and market data streaming, IBKR's Trader Workstation API or Client Portal API are the appropriate channels. ### Can I limit what my agent is allowed to do with the IBKR 3rd Party Web API? Yes. Jentic One is self-hosted by you, so your own rules decide which of the IBKR operations and session credentials the agent may use. You can restrict it to read-only calls such as listing accounts, retrieving open positions and balances, or pulling order and trade history, and leave out order submission and cancellation unless you explicitly add them. Because the partner-approved session credential is held by your instance and injected at execution time, the agent only ever calls the operations you have granted it.