Compare the API’s exact contract and data access with TWS. A quote visible in one interface does not prove the requested API feed is available. Read any extra-subscription message before adjusting connection settings.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Step by step
- 1 Confirm the API app connects to the same TWS session you are inspecting.

A TWS watchlist with live bid, ask and last quotes; the API app must be connected to this same session to see them. - 2 Compare contract type, exchange, currency, and expiry on both sides.
- 3 Read the API response for a permission or data-type message.
- 4 Check the Market Data Connections details referenced by IBKR and the username’s API data access.
- 5 Retry one known contract after correcting the found mismatch.
A practical example
You see a stock price in TWS, but your app asks for an option on that stock. Those are not the same data request. Compare the full product first. If both really ask for the same contract, read the API’s response about its feed access. A screen price is a useful clue, but it is not enough to prove that every app request has the rights it needs.
Screen reference

Mistake to avoid
Common questions
Can a connected API still lack quotes?
Yes. Connection health and data permission are separate.
Should I disable Read-Only API for quotes?
Order request permissions are not the first fix for a market-data access error.