Twitter does not allow monitoring of its API(royal.pingdom.com)
royal.pingdom.com
Twitter does not allow monitoring of its API
http://royal.pingdom.com/2012/07/23/twitter-does-not-allow-monitoring-of-its-api/
2 comments
If I understand Pingdom correctly, they just want to monitor the Twitter API for all their customers that use the API. Pingdom doesn't send tweets for their customers, they just want to notice them when Twitter is lagging.
Sounds suspiciously like they want to avoid having people slam their APIs unnecessarily. They probably don't care how you use their APIs, they just don't want you constantly polling them and/or sending of query bursts just to get some latency stats. Every API hit adds to the load on their servers, and it may also mess up their own internal API statistic gathering.
So they probably want some pre-established legalese that allows them to kick people off who make an unreasonable number of queries for no practical reason.
One developer doing this probably isn't a concern to them, but if thousands of people all over the place do it, that could become annoying.
So they probably want some pre-established legalese that allows them to kick people off who make an unreasonable number of queries for no practical reason.
One developer doing this probably isn't a concern to them, but if thousands of people all over the place do it, that could become annoying.
Add a queue (you already have one right?) so that any messages sent through your api will still get out and you've provided as good of customer service as you're going to get when relying on a 3rd-party API.
I imagine Twitter also wouldn't want all of the sites using it's API to have a message saying "Twitter API is Down", that would be unfortunate for them. I think that also explains the wording of that term.