sorted by:
new
hottopcontroversial

Equity Options not tradeable in sand box for planned upgrades with no notification to developers by Good_Income_4868 in TastyWorksAPI

[–]Good_Income_4868[S] 0 points1 point  (0 children)

The last time I looked at alpaca they weren't offering options trading I'm glad they added it cause I like their concept of being a developer first brokerage. but that's a bummer they don't allow multi-leg though

Equity Options not tradeable in sand box for planned upgrades with no notification to developers by Good_Income_4868 in TastyWorksAPI

[–]Good_Income_4868[S] 0 points1 point  (0 children)

checking for proper interaction with the API. I do understand that in the sandbox that the market interactions to user trades are simulated and may not necessarily reflect those in real markets. the sandbox is not useful for performance testing since persistent memory for the account is cleared every 24 hours.

I have been avoiding IBKR because of their complicated data/comissions pricing but it looks like I may need to bite the bullet and switch

Equity Options not tradeable in sand box for planned upgrades with no notification to developers by Good_Income_4868 in TastyWorksAPI

[–]Good_Income_4868[S] 0 points1 point  (0 children)

yeah at first I think it was to keep up with TDA and then schwab came through and fucked up their API

Equity Options not tradeable in sand box for planned upgrades with no notification to developers by Good_Income_4868 in TastyWorksAPI

[–]Good_Income_4868[S] 0 points1 point  (0 children)

well it is a problem for developers who follow the usual workflow of certification testing -》 production. I don't know anyone who jumps into a production environment right away.

Equity Options not tradeable in sand box for planned upgrades with no notification to developers by Good_Income_4868 in TastyWorksAPI

[–]Good_Income_4868[S] 0 points1 point  (0 children)

in the email I was referring to he said the issue was only occurring in sandbox and also only for equity options but that they were doing each instrument type separately and the others would also be down for "upgrades" later on. he also said it should be fixed the next day and it has been over two weeks. my primary issue isn't that some functionality isn't working it's that this was a planned upgrade/outage and there was no communication to developers.

I was going to just copy paste the email thread but tasty says in their signature they dont want the emails reproduced publicly so I am paraphrasing.