Get Started

Common Issues with Amazon API (and How to Fix Them)

When using PassiveWP’s Amazon integration, you’re relying on Amazon’s Product Advertising API. Sometimes, things can go wrong with the API connection. Here are common Amazon API issues and their fixes:

1. Amazon API Credentials Not Working (Access Denied):
If PassiveWP is saying it can’t connect or you see errors like “AWS Access Key Id does not exist” or “Request is not signed correctly”:

  • Double-check Keys: Make sure you copied the Access Key ID and Secret Key exactly, with no extra spaces. They’re case-sensitive.
  • Associate Tag: Some API calls require a valid Associate Tag (your affiliate tracking ID). Ensure you entered your tag in PassiveWP settings. If it’s missing or wrong, add the correct one (like yourtag-20).
  • API Enabled: Remember, Amazon only enables API access after you’ve made at least 3 qualified sales and your account is fully approved. If you are new and haven’t gotten API access yet, PassiveWP’s keyless mode might cover you for a while. Otherwise, you might actually be getting “access denied” because your API privileges aren’t active. Check your Amazon Associates account: if API is disabled due to lack of sales, you’ll have to wait or use the keyless (which eventually requires a subscription).

2. Reaching API Call Limits (Throttling):
Amazon’s API has a limit on how many requests you can make per day/hour, depending on your sales volume. PassiveWP might hit this if you have many products or frequent updates:

  • Symptoms: Products not updating, or PassiveWP logs showing “Request throttled” or similar. Maybe some products fail to load in search.
  • Solution: Increase the interval of updates. If PassiveWP allows setting update frequency, make it less often. Or reduce number of products actively tracked (My Products list) if possible.
  • Make more sales! (Not immediate, but note Amazon raises your API limit with higher sales).
  • If necessary, stagger API heavy tasks (don’t import 100 products all at once, break into smaller batches).

3. Wrong or Missing Product Data in Displays:
If a product box is showing blank fields or incorrect info:

  • It could be a transient API glitch. Try to manually refresh that product:
    • Perhaps PassiveWP has a “Refresh product” button or option for each product. Use it to force a new API fetch.
  • Ensure the ASIN is correct and valid for the locale you set. A UK ASIN won’t fetch on a US API key for example. If you intend to use non-US Amazon, adjust locale settings (PassiveWP might default to US).
  • Some data might not be available via API (like very new products or certain categories). If PassiveWP can’t retrieve, it might leave it blank. You might have to fill in manually (some plugins let you override fields, check if PassiveWP does).

4. API Key or Secret Changed:
If you regenerated your API keys on Amazon (maybe you thought they were compromised or you rotated them), PassiveWP’s stored keys are now invalid:

  • Update PassiveWP settings with the new Access Key/Secret Key. Save and test connection again.

5. Keyless API Period Expired:
As mentioned, PassiveWP offers a keyless API for a few months for new users. If that expires and you didn’t input your own keys:

  • PassiveWP might start failing to update products or search. Sign up for your own Amazon PA API keys (or extend the keyless service if they offer that).
  • In the interim, products might not update but should still show last known info. Just try to get real keys soon to resume functionality.

6. Specific Error Messages & Fixes:

  • “Invalid Associate Tag”: Your tracking ID might be wrong or maybe you used a tag not connected to your API account. Use the exact tag from your Amazon Associate dashboard.
  • “SignatureDoesNotMatch”: Usually means Secret Key is wrong or incorrectly entered (the signature is a hash of secret key and request). Re-enter Secret Key carefully.
  • “MissingClientTokenId”: Means Access Key ID is missing or wrong. Check that field.
  • “Account not found” or “Invalid account”: Could happen if your Associate account got shut down (hopefully not!). If it did, PassiveWP can’t do much; you’d need to fix your Amazon account status.

7. Amazon API Returning 0 Products for Searches:
If PassiveWP’s product search isn’t finding anything even for broad terms:

  • It might be an API issue: sometimes Amazon’s API requires specifying some parameters. But PassiveWP likely handles that. Possibly your account is restricted or the locale doesn’t have that category.
  • Try a specific ASIN search. If ASIN works but keyword doesn’t, maybe a locale issue or category index. You could try different search keywords or verify on Amazon that those products exist.
  • Could also be throttling (API refusing search calls). If persistent, contact PassiveWP support – might be a bug.

8. Out-of-Stock not updating:
If a product went out of stock on Amazon but PassiveWP didn’t catch it:

  • It might have missed an update if API call failed. Try refreshing product data.
  • Amazon API sometimes doesn’t clearly flag out-of-stock for some items. PassiveWP might rely on price being null or similar to mark OOS. If Amazon still returns a price but the listing says “temporarily out of stock”, PassiveWP might not know. You may have to manually handle some edge cases.
  • Keep an eye on your site or email reports for PassiveWP’s out-of-stock alerts, but cross-verify on Amazon occasionally for critical products.

9. Unable to Import Certain Products (API Restrictions):
Amazon’s API has some category restrictions (for example, it used to not return Kindle books or some digital items via API to non-eligible accounts).

  • If you can’t fetch a product at all, see if it’s a restricted category. You might have to manually link those without PassiveWP displays.
  • Or Amazon API might require you to specify a search index (like “All” vs “Books”). PassiveWP likely abstracts that, but if one category fails, try a workaround like find an ASIN via Amazon’s site and then use PassiveWP’s “Fetch by ASIN” if available.

10. Debug Mode:
PassiveWP might have a debug mode or log (maybe under PassiveWP → Settings → Debug). Enabling it could give detailed error messages from Amazon API. Use it if you can’t figure out what’s wrong; it might tell you exactly the response error which you can then address.

11. Reinstalling/Resetting PassiveWP for API issues:
If all else fails, you could try disconnecting and reconnecting:

  • Remove keys (maybe set blank and save), then re-enter them fresh.
  • Or deactivate and reactivate PassiveWP (though you shouldn’t lose data, have a backup just in case).
  • These steps probably aren’t needed if you diagnose the error message.

12. Contact Amazon Associates Support:
If you suspect your API access is restricted due to some account issue, reach out to Amazon. Sometimes accounts get flagged for low sales (particularly after initial 180 days if you didn’t meet quota they close account). You’d need to reapply or ask for reinstatement to use API again.

13. Keyless API Support:
If you’re using PassiveWP’s keyless service and something’s off (like it should still be active but isn’t pulling data), contact PassiveWP support. They manage that service, so they can check if there’s downtime or account linking issues.

Quick Recap of Fixes:

  • Verify Access Key, Secret Key, and Tracking ID in PassiveWP settings.
  • Ensure your Amazon Associate account is fully approved and API-enabled.
  • Monitor API usage; throttle if needed.
  • Use correct ASINs/locale for searches.
  • Keep PassiveWP updated (in case of any API-related bug fixes in newer versions).

By addressing these common issues, you’ll keep PassiveWP and Amazon’s API on friendly terms, ensuring your product data flows smoothly. And once it’s set up correctly, it tends to run reliably – so a little troubleshooting up front will pay off with a mostly hands-off experience later. Happy fixing! 🔧

What are your feelings
Updated on March 13, 2025