Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.

Чем мы можем помочь?

Примеры запросов: диаграмма Ганта, оплата в рублях, предоставление доступа к папкам...

Rate Limiting API During Development

Комментариев: 3

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Tim Schoffelman

    (Изменен )

    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"

    Is this helpful? 0
    Действия с комментариями Постоянная ссылка
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    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 👍

    Is this helpful? 1
    Действия с комментариями Постоянная ссылка
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Tim Schoffelman

    Thanks Stephen!

    Is this helpful? 0
    Действия с комментариями Постоянная ссылка

Войдите в службу, чтобы оставить комментарий.

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

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.