search

aurbano / robinhood-node

:chart_with_upwards_trend: NodeJS client for Robinhood Trading :fire:
https://aurbano.github.io/robinhood-node
MIT License
694 stars 185 forks source link

Robinhood asked me to stop using their API #97

Closed chiefsmurph closed 4 years ago

chiefsmurph commented 5 years ago

maybe it's time for a change to the headers? also async await support would be great.

alogwe commented 5 years ago

wow, that's kind of surprising.. what did they say?

chiefsmurph commented 5 years ago

@alogwe

We noticed that you may be trading through an API (Application Programming Interface). We’re excited to offer you commission-free trading, but we can’t allow you to transact with an API.

alogwe commented 5 years ago

interesting.. thanks for sharing that. i agree it'd be nice to be able to change headers (also the async/await is always nice to have haha)

thehaitiancoder commented 5 years ago

Can anyone say something more on this? I have been thinking of building a bot for my daily trades, should I get started anyway? What's the chance that Robinhood blocks the access to this API (that one day it simply doesn't answer) or worse close my account?

chiefsmurph commented 5 years ago

@thehaitiancoder here are my thoughts... you might be able to get away with using the Robinhood API for data if you don't put it under too much pressure. I think they really just don't want people executing orders using the API and maybe they'd look the other way just for data? I don't know.

I have been looking into alternatives and these are a few other options I have found:

  1. Alpaca (uses Polygon.io for data)
  2. Interactive Brokers
  3. TD Ameritrade
JoshuaJWilborn commented 5 years ago

I don't understand why they care about the use of the API...As long as you have money and are trading with them. It's not like they are making add revenue. Very strange!

Perhaps what we should do is require user-agent to be set manually on initialization, so everyone has a unique one.

As for async await, I know I'm new here but my opinion is that async await bring there own problems. I would support a refactor to promises over callbacks though. In fact, if the community thinks that would be a good improvement I don't mind doing the work.

aurbano commented 4 years ago

Since this is not an issue of the library directly I'll close it, but discussion is obviously more than welcome as it will be useful for others that find this via search engines.