Rate Limiting API During Development

Does the community or Wrike have any recommendations when working with the API. I've noticed there are some API restrictions (seems to be on both on responses and number of requests) per call or per minute.

I have a timeout set to 60 seconds when i'm completed, but during development, is there a way where we don't have to hit those restrictions and we can just get a sub-set of data back?

Otherwise, any other best practices when developing would be quiet helpful.

ps. I'm working out flattening Wrike data to a single doc for each timelog entry, making it easy for CSV and importing it into excel

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
7 commentaires

PPS - I know Wrike has an export to CSV on a number of their screens (table, timelog, reports, etc.), but none of those screens give me the data I'm looking for, which is the reason for the API work.

Here are the fields I've gathered:

"timelog_id",
"timelog_hours_logged",
"timelog_tracked_date",
"timelog_comment",
"timelog_created_date",
"timelog_updated_date",
"timelog_api_count",
"task_id",
"task_title",
"task_description",
"task_created_date",
"task_updated_date",
"task_permalink",
"task_status",
"client_folder_id",
"client_folder_name",
"meta_Client",
"meta_Sprint",
"meta_Max_Effort",
"user_id",
"user_name"

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Stephen

Hi Tim, there is a limit of 100 requests per minute per single IP.

It is in place to prevent server overload and ensure the trouble-free performance of Wrike for everyone - this is the reason why we do not raise the limit.

If your application encounters an error due to this limit, simply apply a short cool-down period before the next API request and this will help to stop these errors. 


You can make about 100 calls, then wait 1 or 2 seconds before you can make another 100. In essence, with exponential cool-down time, you can ensure that your app makes as many calls as possible. 

Any questions, let me know 👍

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thanks Stephen!

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Stephen,

I have encountered the same problem... and I'm glad that I've found this post... :-)

Greetings from Germany

Torsten

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hey Torsten Mühlhoff, I'm glad to hear that Stephen's reply helped 👍 

 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Have just discovered this limitation when I mass-erased 1000 items from the recycle bin at once and wrike freaked out - which caused me a minor freak out as well - thought I had broken it. 😅 V glad to know I just need to wait a min or two.

Out of curiosity, if this is per IP, I assume that's the WAN IP, not LAN IP?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hey Angela Kennewell, I can see my colleague from the Support team has reached out to you about this 👍

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Rate Limiting API During Development
[this list is visible for admins and agents only]

Haut de la page
Didn’t find what you were looking for? Write new post