Closed littleylv closed 2 weeks ago
I am experiencing the same issue. Sometimes, when I try to make a new call, I receive the 'QuotaExceeded' error, even if the last call to this endpoint was made several hours ago. Apparently, the problem started this week.
@littleylv Have you looked at the rate limit header in the response? Here is a documentation that you can look at to understand how rate limit works. If you still think there is an issue, Please open a support case following the guidance here. Make sure you include a sample response payload in your support case to help expedite the investigation.
Weiling Amazon Selling Partner Services
@weilinggu @puppsupr Whether I request the getShipment interface or getInboundPlan, this issue always occurs Whenever a request is made, regardless of the interval, the following error response will be received: { "errors": [ { "code": "QuotaExceeded", "message": "You exceeded your quota for the requested resource.", "details": "" } ] } Return header parameters: x-amzn-RequestId = 9e9a5949-f046-42ab-9889-7e04f4ce6ac1
Hi @JuCongBoy, Please open a support case following the guidance here. Make sure you include a sample response payload in your support case to help expedite the investigation.
I've also started randomly getting 429 errors on various endpoints in the new FBA Inbound API, regardless of how long its been since I last called the endpoint. Whether or not I get the error seems to be almost entirely random.
I 'have also started getting API rate limit error. It's now very frequent.
{ "code": "QuotaExceeded", "message": "You exceeded your quota for the requested resource.", "details": "" }
Since last one month many apis in new FBA Inbound API version started returning random error.
I am having the same issue. I am grabbing the x-amzn-RateLimit-Limit out of the header and delaying at (int)(1 / rate * 1000). I can run for hours testing on a InboundOperationStatus with no issues. But other times things fail for no reason - like this morning the first call of the day I get throttled out. Something is wrong. No question. We can't go production with this crap. How do you program for all this junk? really ...
I also encountered the same problem. I set the interval to 5 seconds and this situation will occur, and sometimes the error starts with the first request This is the case in the attachment. The interface was not accessed in the printed timestamp, and an error message appeared.
Hi, Each of the operations has different rate limits. Look here in the reference doc. For more information on Rate Limits please look into this doc.
If you still face issues please open a support case as they can help you on this.
closed for inactivity
API: https://developer-docs.amazon.com/sp-api/docs/fulfillment-inbound-api-v2024-03-20-reference#getshipment
response:
I have run Fulfillment Inbound API v2024-03-20 getShipment without errors for one month. But from yesterday, the API return QuotaExceeded error even I did not call getShipment fast. The document says Rate is 2: