3 ms·
do you think you'll have issues with rate limiting and security blocks more generally if you are doing lots of polling from your side on behalf of many integrat
by enos_feedler 3y ago
do you think you'll have issues with rate limiting and security blocks more generally if you are doing lots of polling from your side on behalf of many integrations? One time i wrote a script to poll for changes to my frequent flyer mile account and they banned me and froze my miles. just from a polling script.
- jasonwcfan 3y agoYes - we will run into this problem eventually with a single OAuth application. Having our customers use their own credentials is a workaround but won't work for some platforms that have a really onerous approval policy for new apps. If you or anyone else knows of a solution to this problem let me know, because we haven't crossed that bridge yet.
- drekk 3y agoI worked at [undisclosed Fintech] and their solution was pretty funny. They had a rack of mobile phones on 3G/4G running Android to poll [undisclosed throttle-happy bank]. Was an incredible hackathon project that lasted years.
- nickphx 3y agoEven with oauth applications you will experience rate limiting 'at scale' when many users have authorized your single "application" to perform actions. In my experience, some cases make it easier to have the customer create and provide the oauth application details to help mitigate rate limits, review requirements, and access restrictions.
- jasonwcfan 3y agoYeah we do offer that actually! For customers with significant volume it'll help lighten the load