Minimum delay between calls to API?

aus · 2017-10-06T14:28:39.329Z

Hi

I have an issue with performing API calls in quick succession.

Whenever I

POST account_activity/webhooks
and immediately afterwards
POST account_activity/webhooks/:webhook_id/subscriptions

the second POST results in an error, whereas if I wait 3 seconds before the second POST it all works fine.

Is there an official minimum delay between API calls that needs to be respected?

Thanks

joncipriano · 2017-10-25T22:55:54.295Z

Long delayed response here.

Here is a Node script that makes these calls consecutively. It’s important to wait for the first request to complete before continuing when using an asynchronous language like javascript. Perhaps this is the issue being encountered.

github.com

twitterdev/twitter-webhook-boilerplate-node/blob/master/example_scripts/webhook_management/update-wehbhook-url.js

/**
 * UPDATE WEBHOOK STEPS
 * 1. Retreive current webhook config
 * 2. Remove subscription for user on current webhook config
 * 3. Delete current webhook config
 * 4. Create new webhook config with new URL
 * 5. Add subscription for user
 */


var nconf = require('nconf')
var request = require('request')


// load config
nconf.file({ file: 'config.json' }).env()

// twitter authentication
var twitter_oauth = {
  consumer_key: nconf.get('TWITTER_CONSUMER_KEY'),

This file has been truncated. show original

aus · 2017-10-26T11:37:33.491Z

Hi Jon

thank you for your reply. I do indeed make sure that a request is completed before the next one is started. I suspect it’s an issue related to the eventual consistency of Twitter’s storage. If this is the case, it might be worthwhile trying to avoid this problem, maybe by routing subsequent webhook-related requests to the same node (just guessing…).

joncipriano · 2017-10-26T18:03:36.310Z

It is possible that it could be a delay in data replication, but 3 seconds sounds excessive. We haven’t had this issue reported by others, but I’ll keep an eye out for it. May I ask what region of the world you are in? It would help identify the data center you would be hitting.

aus · 2017-10-27T10:47:27.076Z

3 seconds is my “safe” request delay: last time I tried it was for sure larger than 1 sec.
Due to the request limits I could not perform many tests and I decided to play it safe with a long delay.