timothygoltser

5 ms·

1. 1.▲
   GovDash (YC W22) Is Hiring Senior Engineers (Product and Search) in NYC(workatastartup.com)

   1 points by timothygoltser 8mo ago
2. 2.▲
   by timothygoltser 4y ago

   Hey Charles, we're really excited to be working on tooling to make data sharing easier for companies and their customers! The activation energy for setting up robust direct-to-customer pipelines is still too high on the provider’s end
3. 3.▲
   by timothygoltser 4y ago

   Thank you - we'll submit a proposal shortly!
4. 4.▲
   by timothygoltser 4y ago

   Thanks!
5. 5.▲
   by timothygoltser 4y ago

   Hey all, one of the co-founders of Pipebird here - I'll be around to answer any questions you might have. Would love to hear your feedback!
6. 6.▲
   by timothygoltser 5y ago

   We collect a user's credentials (usernames + passwords) and exchange them immediately for access and refresh tokens. We use the term "credentials" as we've seen it used colloquially - access and refresh tokens certainly
7. 7.▲
   by timothygoltser 5y ago

   Thanks! Teller looks really cool - there's definitely a real market for what you're doing, though I don't envy your position having to deal with the big banks given how misaligned incentives are in the retail banking industry
8. 8.▲
   by timothygoltser 5y ago

   TD Ameritrade is the biggest brokerage we deal with that has a documented public API intended for external use, but the documentation isn't entirely accurate and the rate limits on some endpoints are fairly restrictive by default (120
9. 9.▲
   by timothygoltser 5y ago

   We provision both a live and sandbox app with 3 free test links each so that you can test out the API after signing up - we'll make sure to display that more prominently on our site/in our docs to avoid confusion on this point. Th
10. 10.▲
    by timothygoltser 5y ago

    Thank you! We're going to be adding support for options sometime next week. IB is also on our roadmap, though we don't have an exact timeline for an integration yet.
11. 11.▲
    by timothygoltser 5y ago

    Definitely - we've gotten this feedback from several of our users and it's a high-priority item for us. We'll be adding the ability to limit scopes on a per-app basis this week.
12. 12.▲
    by timothygoltser 5y ago

    We've had the same experience in 2022. An afternoon with an HTTPToolkit interceptor is usually all it takes to reverse engineer a brokerage's API; we spend most of our time paving over various brokerage-specific idiosyncrasies and
13. 13.▲
    by timothygoltser 5y ago

    Absolutely. We don't have a timeline on it as of yet, but we've received several requests for IBKR support (especially from developers building apps that serve non-US markets), so it's something we'll be looking into soo
14. 14.▲
    by timothygoltser 5y ago

    You're right that most retail investors don't pay attention to the specifics of how margin requirements are calculated. To my knowledge, the only brokerage that's readily accessible to retail investors that provides SPAN marg
15. 15.▲
    by timothygoltser 5y ago

    Agreed - there's no fundamental reason interfacing with traditional brokerages should be as difficult as it is today. We're working to form relationships with all of the brokerages that we integrate with and are advocating for the
16. 16.▲
    by timothygoltser 5y ago

    While I'm not fully qualified to comment on this (I'm not a lawyer/have no formal experience with securities law), my understanding is that it would depend on if the trader in question is providing investment advice. The SEC
17. 17.▲
    by timothygoltser 5y ago

    We do sanctioned integrations with brokerages wherever OAuth integrations are available such that we don't have to collect credentials, but for the ones without public APIs we do need to collect credentials (though we never store them)
18. 18.▲
    by timothygoltser 5y ago

    In a sense. There are certainly protections they can implement against non-browser clients; what I meant is that it would be more difficult for them to implement the usual sorts of defenses you see against screen scraping since the surface
19. 19.▲
    by timothygoltser 5y ago

    It depends on the nature of the activity that got the account blocked - we place limits on the types of legitimate account activity that are likely to get a user blocked (sending too many orders too quickly, sending orders that could be bat
20. 20.▲
    by timothygoltser 5y ago

    That's a fair point - we've been trying to determine the best way to compress "using reverse-engineered private APIs in violation of their terms, but in practice brokerages don't really take enforcement actions against t
21. 21.▲
    by timothygoltser 5y ago

    While we try to form relationships with all of the brokerages we integrate with (including the ones we reverse engineer), we do still have to do the abuse/block dance with their protective systems occasionally. We've found that cu
22. 22.▲
    by timothygoltser 5y ago

    Different brokerages take different positions on these sorts of integrations - some go after all third-party integrations aggressively (including screen scrapers), while some will turn a blind eye as long as you're not abusing their pl
23. 23.▲
    by timothygoltser 5y ago

    Thanks!
24. 24.▲
    by timothygoltser 5y ago

    We see ourselves as somewhat of a spiritual successor to TradeIt - we're trying to provide high-quality access to brokerage accounts so that people can build better investing apps on top of existing brokerages. In terms of pricing: we
25. 25.▲
    by timothygoltser 5y ago

    Thanks! Where possible, we integrate with brokerages' public APIs (we refer to these as "sanctioned integrations"). Brokerages like TD and Alpaca implement OAuth such that we can get delegated access to user accounts, but tha