IBKR Short Sale Data still limited to sample sids after paid plan upgrade

Technical Help
#1

Hi, I upgraded to the paid QuantRocket plan on April 22, 2026, and regenerated my license key afterward. The new key is installed, and the license profile loads normally.

I’m trying to use QuantRocket’s IBKR Short Sale Data, but it still seems limited to sample sids. I’m running QuantRocket on Windows with WSL2 and Docker Desktop.

Commands used:

  • quantrocket fundamental collect-ibkr-shortshares --countries usa
  • quantrocket fundamental collect-ibkr-borrowfees --countries usa
  • quantrocket fundamental ibkr-shortshares --sids ... --start-date ... --end-date ... --aggregate
  • quantrocket fundamental ibkr-borrowfees --sids ... --start-date ... --end-date ...

What I see:

  • AAPL returns rows (already part of free sample)
  • Other symbols such as ASTS and ACHR return:
    • msg: No shortable shares data match the query parameters
    • msg: No borrow fees data match the query parameters
  • Earlier quantrocket-fundamental logs included:
    • no active subscription found, filtering to free sids

What do I need to do to get the full IBKR Short Sale Data working in my deployment after upgrading? If there is an entitlement refresh, account-side activation, or deployment-side step beyond setting the new license key and forcing a license refresh, please let me know. Thanks.

#2

No extra step should be required.

To verify the basics, first run quantrocket license get and make sure it shows an active license. If the license_type key is populated in the output, that means it is active.

...
software_license:
  license_type: Individual Non-Professional
...

Next, make sure to have Flightlog open while collecting the data so you can see the log output, as that will tell you when the collection is completed. The free data is collected very quickly, but the full dataset should take longer. Make sure it has finished before you try querying.

If the "no active subscription found, filtering to free sids" occurred before you upgraded, that's expected, but if it occurred after you upgraded, then the issue is the license. However, that shouldn't be the case assuming the license key you entered is for the same account with the paid subscription.