[#894] 429 API calls limit exhausted

Bug Reports
,
1

Migrated from Redmine #894 | Author: Bob LS
Status: New | Priority: High, I’m very impatient | Created: 2022-06-16

Good afternoon, I have contacted your live support about this issue and they have referred me here.

We believe we have made only around 1500 API calls to your service today, but you have blocked further requests with a 429 error. Your support team advised we have racked up 9k requests, but we cannot reconcile this with our data.

Could you please investigate this and advise which endpoints have been used and from which IP address they have come. For security reasons please do not post the our company name stub in the URL nor the IP publicly, could you please message me privately with the specifics.

Thanks

2

Redmine Admin wrote:

please provide your company login

3

Bob LS wrote:

How can I provide this to you without it appearing publicly here?

4

Redmine Admin wrote:

no way, then you have to contact our livehelp

5

Bob LS wrote:

I already did that and they sent me to you. Telling me they could not provide the data, and you could.

6

Redmine Admin wrote:

this is public forum, if you don’t want your login to appear here then we can’t help you. Support is able to provide you API usage statistics log, please contact them again (you can use this discussion as reference of course).

7

Bob LS wrote:

Unfortunately your agent Stacy is saying otherwise. See attached.

8

Bob LS wrote:

Your request was received, thank you
12:41
But we do not answer API questions via the chat
As per my check, our developers states that we do not collect/provide such statistics for security reasons

9

Redmine Admin wrote:

she is telling you we cannot provide you list of api calls, only number of calls which is correct.

10

Bob LS wrote:

So how can I get such information?

11

Redmine Admin wrote:

you can do api calls log yourself if you need this info

12

Redmine Admin wrote:

(api calls may contain sensitive data and we are not able to log this according to GDPR and best practices)