Developer Support Ticket 260821-000067 Stalled — Production OAuth invalid_grant
Summary: mydbmbu_52 is seeking help from the eBay Developer Community regarding a stalled technical support case (260821-000067) related to a Production OAuth authorization-code issue. They consistently receive an 'invalid_grant' error, despite verifying their environment and configurations. Despite providing the required diagnostics, they are awaiting further guidance. They noted a similar issue reported by another developer but acknowledge the cases may have different root causes. They request further escalation of their case for resolution.
Hi eBay Developer Community,
I’m requesting assistance with an existing eBay Developer Technical Support case, 260821-000067, involving a Production OAuth authorization-code exchange.
The token endpoint consistently returns:
invalid_grant — “the provided authorization grant code is invalid or was issued to another client”
Developer Technical Support requested sanitized cURL examples and additional diagnostics, which we provided. We also sent a follow-up, but we are still waiting for further technical guidance.
We have verified the Production environment, Client ID/keyset association on our side, RuName/redirect_uri, authorization-code handling, encoding, and immediate exchange within the code expiration window. Fresh authorization codes have still produced the same invalid_grant response.
We have paused additional authorization attempts while awaiting guidance so we don’t continue generating and consuming authorization codes unnecessarily.
Could an eBay Developer Support moderator please check or escalate DTS case 260821-000067 to the appropriate OAuth/API technical team?
I can provide additional sanitized diagnostics privately through the existing support case if needed.
Thank you.
mydbmbu_52
OP1 week agoAdditional context: I found another recent eBay Developer Community report showing a similar Production OAuth invalid_grant / “issued to another client” symptom after the developer verified their Production keyset and repeated the consent flow.
Their failure occurs during a refresh-token grant, while ours occurs during the authorization-code grant, so I understand these are not necessarily the same root cause. However, the similarity may be useful when investigating whether there is a broader Production OAuth association issue.
Our DTS case remains 260821-000067.