Best practices for Amazon SPAPI extract with rate limit exceeded errors

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Guide or best practices for handling rate limit exceeded errors when setting up Amazon SPAPI extract with multiple streams enabled.


Question

Hey Y’all, I’m working on setting up a Amazon SPAPI extract with many of the streams enabled. Unsurprisingly I’m running into rate limit exceeded errors. Is there a guide or set of best practices I should be following? I’m not sure if there is any info I can provide to be more specific as it seems the answer is to “do extract – but slower.”


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["amazon-spapi", "rate-limit-exceeded", "best-practices", "extract"]
2

Did you check https://docs.airbyte.com/connector-development/config-based/understanding-the-yaml-file/error-handling#backoff-strategies? The best is to implement the correct backoff

3

Thanks Marcos, This looks really helpful. is it possible to set a proactive rate limit on my side, or should I just be fine hitting the limit and backing off?

4

hit the limit and backoff is the best choice, create a proactive rate-limit is much more complex :stuck_out_tongue:

5

<@U01MMSDJGC9> How would you configure the suggested backoff above within the certified Amazon Seller Partner?