Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,658
Community Members
 
Community Events
176
Community Groups

False 429 error on first API query

Edited

Some users of our app Bridge24 have that issue:

They need to query informations about a "member", using that endpoint: 

GET https://trello.com/1/members/(idMember)?key=(myKey)&token=(myToken)&fields=fullName,username,status,avatarUrl,memberType

They receive a 429 error in return, "too many requests".

But, in that case, it's the first request!

Also, I get these in the reasponse headers:

X-Rate-Limit-Api-Key-Remaining: 297
X-Rate-Limit-Api-Token-Remaining: 97
X-Rate-Limit-Member-Remaining: 372

How can it be a 429 ?

I think that it occurs for people that are not in a workspace, they only have been invited to other workspaces, but they don't see them in the list.

I think that the good response should be "403 forbidden".

1 answer

Ok, let me add some details....

After more testing, we really had to do 100 calls to "members", so the 429 message can be ok, but something went wrong.

The X-Rate-Limit-Api-Token-Remaining header is going from 100 to about 25 after, 10 secondes, it is reset to 100.

We clearly see that the response move from 100, 99, 98, ... 25, 100.

But, it looks like the 100 returned is not applied server-side, because 25 query later, we start getting "429". 
So, I suppose that, somewhere, the limit continue to move at 24, 23 , 22... even if the header we get in response was  reset to 100 after the X-Rate-Limit-Api-Token-Interval-Ms limit.

I have the same issue on the same endpoint. Although the response headers indicate, that the rate limit has been reset, the API does not act accordingly. Sometimes, I even get 429 on the first call after waiting for several minutes for a reset.

Edit: I guess, I missed that there is an extra limit for /1/members of 100 request per 900 secondes.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events