Dark

Check out our API

FSRCY
FIRST RES LTD UNSP/ADR
stock OTC

Inactive

Dec 4, 2018

115.13USD-26.971%(-42.52)100

Pre-market

0.00USD-100.000%(-157.65)0

After-hours

0.00USD0.000%(0.00)0

Overview HistoricalExchangesShortsTrends

FSRCY Reddit Mentions

Subreddits

Limit Labels Price

We have sentiment values and mention counts going back to 2017. The complete data set is available via the API.

Take me to the API

FSRCY Specific Mentions

As of Aug 11, 2026 12:58:25 AM EDT (1 min. ago)

Includes all comments and posts. Mentions per user per ticker capped at one per hour.

375 days ago • u/iqzium • r/algotrading • 403_errors_for_random_stocks_on_interactive • Data • B

The IB client portal API has an endpoint trsrv/stocks which accepts a comma separated list of symbols and returns a JSON that has exchange and conid information for each symbol.
Interactive Brokers doesn’t give you a list of supported symbols programmatically, so I get this list from elsewhere then pipe them into this endpoint so I can see which stocks are supported for my algorithm.
A normal, valid symbol (e.g. AAPL) will return a JSON structure.
An invalid symbol (e.g BLAHBLAH) will return an empty JSON element.
However I’m finding that there are some symbols which return 403 errors. This complicates processing because you pass \~100 symbols through a single API call and the whole call returns with a 403 because of one symbol.
Did anyone else encounter this? Is there a way to work around it without hardcoding? Some examples are ESRCF and FSRCY. I’ve opened a bug report with their team last month but haven’t heard back beyond they will look into it with their security team and to ignore these symbols.

375 days ago • u/iqzium • r/algotrading • 403_errors_for_random_stocks_on_interactive • Data • B

The IB client portal API has an endpoint trsrv/stocks which accepts a comma separated list of symbols and returns a JSON that has exchange and conid information for each symbol.
Interactive Brokers doesn’t give you a list of supported symbols programmatically, so I get this list from elsewhere then pipe them into this endpoint so I can see which stocks are supported for my algorithm.
A normal, valid symbol (e.g. AAPL) will return a JSON structure.
An invalid symbol (e.g BLAHBLAH) will return an empty JSON element.
However I’m finding that there are some symbols which return 403 errors. This complicates processing because you pass \~100 symbols through a single API call and the whole call returns with a 403 because of one symbol.
Did anyone else encounter this? Is there a way to work around it without hardcoding? Some examples are ESRCF and FSRCY. I’ve opened a bug report with their team last month but haven’t heard back beyond they will look into it with their security team and to ignore these symbols.

Share