Skip to main content

Hello,

We are progressing on the synchronization of the Analytics part, over the last 30 days, for accounts. For this, as seen together, we use the /reports routes in GET then PUT.

We are facing several problems. The limit is not 200 calls per minute for these routes but 200 + a 1 second delay between each. We need 2 requests: GET then PUT. That is 4 seconds for 2 requests for an analysis request. First limit. Second limit, in order to collect information from the last 30 days, or even more, we need a significant delay: around 20 hours. However, it seems that our "massive" requests, by internal choice, trigger this error:

Could not resolve host: api2.frontapp.com.

Are we, suddenly, considered as "spammers" and therefore blocked after a number of requests? In this case how should we proceed if we want to refine our filters and "consume" requests.

Thanks in advance.

The /analytics/reports endpoint has an additional "burst" rate-limit associated with it:

 

https://dev.frontapp.com/docs/rate-limiting#additional-burst-rate-limiting

 

 A POST request to that endpoint can only be made once every second.

 

The error Could not resolve host: api2.frontapp.com sounds like a DNS error and potentially a limitation from not caching DNS lookups.  Is it possible for your team to check what DNS server is used for these API requests?

 

--Evan


Reply