Too Many Active Keys

[xbaha]

i am getting this content error:

  | Name | Value | Type
-- | -- | -- | --
  | Content | "{\n  \"errors\": [\n    {\n      \"message\": \"Too Many Active Keys\",\n      \"code\": \"InvalidInput\"\n    }\n  ]\n}" | string

The same call was working for days, suddenly I am getting this error on ALL my calls????

[yswenli]

POST /reports/2020-09-04/reports GET_FBA_FULFILLMENT_INBOUND_NONCOMPLIANCE_DATA { "errors": [ { "message": "Too Many Active Keys", "code": "InvalidInput" } ] }

[billsquall]

POST /reports/2020-09-04/reports GET_FBA_FULFILLMENT_INBOUND_NONCOMPLIANCE_DATA { "errors": [ { "message": "Too Many Active Keys", "code": "InvalidInput" } ] }

me too

[xbaha]

are you getting this for reports or everything?

[mainak777]

I am facing the same issue for Orders API "{\n \"errors\": [\n {\n \"message\": \"Too Many Active Keys\",\n \"code\": \"InvalidInput\"\n }\n ]\n}" GET/orders/v0/orders Is there any solutions. Yesterday it was working fine

[RatebHabbab]

I'm facing the same issue for the following APIs: order, catalog, inventory, sales and reports.

[edward-rafalovsky]

i am getting this content error:

  | Name | Value | Type
-- | -- | -- | --
  | Content | "{\n  \"errors\": [\n    {\n      \"message\": \"Too Many Active Keys\",\n      \"code\": \"InvalidInput\"\n    }\n  ]\n}" | string

The same call was working for days, suddenly I am getting this error on ALL my calls????

Same problem on all the types of requests, Feeds, Orders, etc

[brenjt]

I had the same problem with all my API calls. I can't find any way to get around it or a way to revoke/delete old keys.

[moltar]

We are getting the same across all regions.

[ganeshkrishnan1]

Same error. is anyone even looking at the errors? Our dev work is stuck and Amazon has given us till September to migrate from MWS

[isaacngordon]

I'm experiencing this same issue. I have production code that has been running fine since my last deployment several weeks ago, and now all of a sudden I'm receiving "Too Many Active Keys" error message on all api calls.

[pprbhm]

Hello, Thank you for bringing up this issue as multiple people are facing it. Can @xbaha or @brenjt open a case with Developer Support team here so that it can be worked on more detailed level.

[vicky-3001]

Facing this issue for all api calls. This is strange, still no one is working on the fix

[xbaha]

@pprbhm this issue is not related to me only, It's happening to many, so i don't think opening a case would do anything.

[pprbhm]

@pprbhm this issue is not related to me only, It's happening to many, so i don't think opening a case would do anything.

Hi @xbaha I understand that but without having to know requestID's, sellerID and their permissions, It's not possible to identify an error. Also i would not advise to put such details on Public forum hence suggested to open a case and we can take it from there, Once finding the error we can update the forum on it. Once you have created the case you can let me know the case number and we can work through it.

[xbaha]

@pprbhm the issue is not related to a sellerId, requestId nor permissions, what used to work suddenly stopped for many on ALL API calls. If Amazon is following Github bugs, they should do something, opening a case from my experience has a painful waiting for months without any actual results.

[pprbhm]

Hello @xbaha Some issues are seller/vendor specific so that needs a personal attention. I am sorry to hear you had bad experience with case with developer support team. The currently discussed issue is identified and backend team is working on fix for it.

[xbaha]

@pprbhm Thanks for the update!

[ganeshkrishnan1]

I have raised a request with the request id, time stamp and path.

I always dread raising requests on Amazon. Their response is always something like "can you please provide additional data including moon phase and chair taste when you submitted this request"

[jhullparkseed]

Though I opened a similar but different thread I'll jump in here to track. I agree that it seems more a general bug/error since yesterday all was good and today not. With an official announcement from Amazon on MWS, there is pressure to change and I'd feel better switching to an API that is either stable or the developers are quick to follow up. Glad to read a team is on it.

[parvathm]

Hi all,

This issue is resolved. Please try making a request and let us know if you are still facing same issue. Sorry for the inconvenience caused.

Thanks, Parvathm, Selling Partner API Developer Support.

[xbaha]

@parvathm Thanks for the quick response, it's resolved for me.

[brenjt]

It's working for me too. Thank you!

[jhullparkseed]

me too. whew!

[FloderCC]

Me too. Please help.

[glukoid]

no line of code of my application was changed but suddenly I got the same error:

{ "errors": [ { "message": "Too Many Active Keys", "code": "InvalidInput" } ] }

if anyone could help me to understand what this error about and how to solve it.

[parvathm]

Hi @glukoid,

"Too Many Active Keys" is due to an issue on our end. We are actively working to fix it. I will update once the issue is resolved.

Thanks, Parvathm Selling Partner API Developer Support.

[ShivikaK]

Hello everyone,

The issue causing "Too Many Active Keys" has been resolved and you should be able to make a successful request. Please let us know if error persists.

Thanks, Shivika Khare Selling Partner API Developer Support

[moltar]

Has it been fixed permanently or should we create defence code for it in the future? @ShivikaK

[ShivikaK]

Hello @moltar

We are currently fully investigating the root cause and working on fixing this issue permanently. If the error starts occurring in the meantime, please update here or notify us via Support case.

Thanks, Shivika Khare Selling Partner API Developer Support

[traceremick]

@ShivikaK started receiving this error today for the first time. Anything we can do on our end to resolve this issue?

[ShivikaK]

Hello @traceremick

Are you receiving the Too Many Active Keys exception or is it a different error message?

Could you share some more details regarding this?

Thanks, Shivika Khare Selling Partner API Developer Support

[traceremick]

Hello @traceremick

Are you receiving the Too Many Active Keys exception or is it a different error message?

Could you share some more details regarding this?

Thanks, Shivika Khare Selling Partner API Developer Support

Apologies for lack of supporting info.

I was receiving the same exception, "Too Many Active Keys" for at least an hour today while accessing the catalog api. Though it appears to be fixed now with no changes on my end.

[ShivikaK]

Hello @traceremick

Thank you for providing the details. The team is investigating the cause for the errors as the issue was fixed and should not have occurred again.

If you start getting the error again, please share the timestamp of the first such request and which API you were trying to access.

Thanks, Shivika Khare Selling Partner API Developer Support

[jhullparkseed]

With such a quick response can we also look at the Authorization errors that many people are having with the FEEDS apis. I can, for example use ORDERS like getOrder just fine and yet createDocumentFeed gives me an error using the same authentication steps. I've put a support case in (ID8494311371) but have gotten no real response and I have provided good detail in the case.

I am not the only one with this issue and it would be great if y'all gave some indication that someone is looking at this issue (and yes I realize it is not the same as this thread, burt you at least responded to a user developer)

[ShivikaK]

Hello @jhullparkseed

Thank you for reaching out and for opening the support case for your issue.

Your support case has been received by us and is currently being reviewed and investigated.

Please continue monitoring the support case for next steps and further updates.

Thanks, Shivika Khare Selling Partner API Developer Support

[saleweaver]

Hello @jhullparkseed

Thank you for reaching out and for opening the support case for your issue.

Your support case has been received by us and is currently being reviewed and investigated.

Please continue monitoring the support case for next steps and further updates.

Thanks, Shivika Khare Selling Partner API Developer Support

Hi Shivika,

I'm the author of https://github.com/saleweaver/python-amazon-sp-api. I had the error too, it seemed to me that the error occurs when multiple services are requesting access tokens from different instances at a high pace; it seemed to happen first when we requested tons of reports from a SQS listener function for the REPORT_PROCESSING_FINISHED_NOTIFICATION.

Can you check if the user agent for many of the requests starts with python-sp-api? I since have implemented key sharing using secrets manager, which stopped the error for me - but may not be ideal for every use case.

Thanks!

[github-actions[bot]]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

[kdcurrie]

Hi I am now receiving this error using the DSP API. I will open a support ticket but now there seems to be an issue using DSP.