Google is your friend.
Here’s one to get you started...
“The campaign’s exhaustive use of Facebook triggered the site’s internal safeguards. “It was more like we blew through an alarm that their engineers hadn’t planned for or knew about,” said St. Clair, who had been working at a small firm in Chicago and joined the campaign at the suggestion of a friend. “They’d sigh and say, ‘You can do this as long as you stop doing it on Nov. 7.’ “
[1] https://mobile.nytimes.com/2013/06/23/magazine/the-obama-cam...
There are also enough stories from FarmVille and far smaller apps and the access they had. I wonder if anyone remembers running into API rate limits in the 2010-2012 timeframe?
I remember being as surprised by the API access as many of the testimonials we now hear. I had initially implemented rate limiting on my side. After never running into any problems, I gradually reduced the delays to 0 without ever hitting any limits. But I only ever accessed maybe a few dozen GB of data, not the 100+ million accounts others apparently got.
It may also have been important that CA saved all the data with no expiration policy. The API limits may have been set based on the usage pattern the ToS prescribed, namely never caching data for more than 24 hours. If you save and reuse the data instead, you save a lot of duplicate API calls and get new data instead.