What happens when Amazon API rate limits are reached?

Amazon enforces strict limits on how frequently its APIs can be accessed. These limits are designed to ensure fair usage and maintain system stability across all applications accessing Amazon’s services.

MerchantSpring operates within these limits when retrieving marketplace data. If the rate limit is reached, API requests may temporarily pause until additional request capacity becomes available.

How API Rate Limits Work

Amazon assigns each API endpoint a specific request allowance over a defined time window.

For example:

• A certain number of requests per second
• A defined number of requests per minute

When this threshold is reached, additional requests must wait until the limit resets.

How MerchantSpring Handles Rate Limits

MerchantSpring includes mechanisms to manage API rate limits efficiently.

These include:

• Request queueing
• Automatic retry logic
• Data retrieval prioritization

When the limit resets, queued requests are processed automatically.

How This May Affect Reporting

If API rate limits are reached, you may notice:

• Slight delays in data updates
• Reports updating later than expected
• Temporary gaps in recently updated metrics

Once the API capacity resets, MerchantSpring continues retrieving data normally.

Notes: 

• Rate limits are controlled entirely by Amazon.
• Larger accounts may require more API requests due to higher data volumes.
• Temporary delays are usually resolved automatically.