What causes an Amazon API connection to fail?

MerchantSpring relies on Amazon’s APIs to retrieve marketplace data such as orders, financial events, product information, and advertising metrics.

Occasionally, the connection between MerchantSpring and Amazon may fail temporarily. This usually occurs due to authentication issues, API restrictions, or account configuration changes.

---

Common Causes of API Connection Failures

• Expired Authorization
  Amazon connections require active authorization tokens. If these expire, MerchantSpring will lose API access until the connection is reauthorized.

• Permission Changes
  If permissions within Seller Central or Vendor Central change, the integration may lose access to certain datasets.

• API Rate Limits
  Amazon restricts how frequently APIs can be accessed. When limits are reached, requests may temporarily fail or be delayed.
  
  MerchantSpring automatically retries requests once limits reset.

• Account Security Updates
  Security changes such as:

• • Password updates

  • Two-factor authentication changes

  • Administrator role changes

may require reauthorization of connected applications.

• Amazon Service Interruptions
  Occasionally, Amazon APIs experience temporary outages or maintenance periods that interrupt data access.
  
  These interruptions are usually resolved quickly.

---

Steps to Check Your API Connection

1. Navigate to Settings → Channels
2. Locate the Amazon connection
3. Verify the status shows Connected
4. If the connection shows Disconnected, select Reconnect
5. Follow the authorization prompts

---

Notes: 

• Most connection interruptions are temporary.
• MerchantSpring automatically retries failed API requests.
• Reconnecting the account usually resolves persistent connection issues.

---

Troubleshooting

If the connection continues to fail after reconnecting, please contact support@merchantspring.com.au.