rate_limit error, How to make sure that my limit is 5000 calls?

Answered

Follow

Alejandro Carrasquilla

• August 31, 2012 20:57

I am getting rate_limit error: "error_propagate":false,"error_parameters":{},"error_detail":null,"error_description":"rate_limit","error":"rate_limit">

I don't think we are hitting 5000 calls an hour, but I do think we may be over 250. How do I make sure that my call is not marked as "Rate Limited".

I am using C sharp to connect to Podio.

Any help would be appreciated .

Thank you

Alejandro Carrasquilla

0

• 

  Andreas Haugstrup Pedersen

  • August 31, 2012 21:01

  You can see on each operation if it's using the lower limit or not. E.g. see the 'Rate-limited' note at the top right of https://developers.podio.com/doc/items/filter-items-4496747 

  Here's another operation that is not using the lower limit (i.e. it doesn't have the 'Rate-limited' note): https://developers.podio.com/doc/items/get-item-22360

  0

  Comment actions Permalink
• 

  Alejandro Carrasquilla

  • September 04, 2012 14:19

  Thank you for explaining that. Also, Is the limit per Call type? Like 249 calls to update Item and 249 calls to delete item would be fine?, Also  Once the limit is reached, Does it take an hour for the ban to be lift.? Or When does the time actually starts counting? Also would  it be possible to raise the limit for an application? 

  Thank you

  0

  Comment actions Permalink
• 

  Christian Holm

  • September 05, 2012 14:41

  Hi Alejandro

  You have 250 calls total for the "expensive" operations, so either 250 deletes or 250 updates or any combination totaling 250 calls. It is indeed per hour. The counting starts with the first call and resets every hour.

  It would be good to know a little about your usecase, so we can recommend the best approach to not having to do so many "expensive" calls. 

  If needed we can also increase the limits, within reason.

  0

  Comment actions Permalink
• 

  Nick Worth

  • November 09, 2012 01:28

  Is there any way around this during development? It seems like anything I want to do is going to be intensive considering I'm loading items and manipulating them publicly.

  0

  Comment actions Permalink
• 

  Andreas Haugstrup Pedersen

  • November 09, 2012 06:15

  Are you pulling out items one-by-one? If you're getting a lot of items from the same app it's often better to use Filter Items to fetch all the items in one API call.

  Same goes when saving items. If you are manipulating values in several fields you'll want to use Update Item instead of updating each field value individually.

  0

  Comment actions Permalink
• 

  Nick Worth

  • November 09, 2012 06:24

  Ya I was using the filter() but I noticed it say rate-limit as well and while in development I'm refreshing a lot so i had just hit the limit and had to wait to continue working.

  0

  Comment actions Permalink
• 

  Ajmal VH

  • November 09, 2012 10:46

  If it is automated operations i overcome this by sleeping the process for a while ie: total calls available 5000/ 3600 sec = 1.38 sec sleep between each call.  When the 5000 api calles are over the other 5000 is ready then.

  0

  Comment actions Permalink
• 

  Stephan Vierkant

  • May 16, 2013 17:09

  I'm trying to monitor how many requests my sync script uses. Every time I run my script, Podio::rate_limit_remaining() decreases with 5, but when I check the debug log (Podio::$debug = true;), I only see 3 requests.

  Why is there a difference?

  0

  Comment actions Permalink
• 

  Andreas Haugstrup Pedersen

  • May 16, 2013 17:15

  The debug log doesn't log authentication requests because you don't want your credentials logged anywhere. So if you are authenticating as two different apps for example that would explain the difference.

  0

  Comment actions Permalink

Please sign in to leave a comment.