-
Notifications
You must be signed in to change notification settings - Fork 58
Troubleshooting & FAQ
Twitter's REST API limits users to 180 requests per 15-minute window; BotOrNot uses this rate limit as well. As with Twitter's REST API, responses from BotOrNot include the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers.
If you would like BotOrNot access without rate limits, contact us about our commercial offerings. You must have access to Twitter data beyond the public REST API in order for increasted BoN rate limits to be useful.
9 times out of 10 this error happens because you're missing something the backend code is looking for in the request body. Make sure the following are true:
- The body of your POST request is a JSON string and not form-data
- The
contentfield of the request object is an array of tweet objects, each of which contain their user objects (this is how they usually come from Twitter) - The
user_idandscreen_nameare provided in themetaobject and they refer to the user whose timeline is being analyzed
This is often due to an issue at the ISP level. We've seen this with requests coming from certain countries; if possible, try the request with a server or proxy located in the US and see if it works.
This error happens when our web server is not forwarding requests to the BotOrNot service. This error most often occurs when we are pushing an update to the backend code, but sometimes happens when the service is over capacity. In either case, wait 60 seconds and try again. Updates may take up to 5 minutes to complete, so be patient if you see this error.
As discussed in an issue, this is due to an issue with your Twitter API keys (not Mashape). Check carefully for typos introduced by copy-pasting. You can troubleshoot your Twitter API connection with the Tweepy API object property: bom.twitter_api. Try something like bom.twitter_api.verify_credentials().