URGENT: Marketplace Deletion Endpoint Validation Failing & Support Button Broken

Hello,

I have been trying for over a week to get my production keyset enabled by completing the Marketplace Account Deletion endpoint validation, but it is consistently failing. I have confirmed with 100% certainty that my code is correctly implementing the challenge-response flow as per your documentation.

Furthermore, the "Activate Support" button on the developer portal is broken and does nothing, so I cannot open a formal support ticket.

Here is the proof from my server logs showing a perfect, successful response to one of the many validation attempts:

My Endpoint URL: https://unpeaceful-nonburnable-milda.ngrok-free.dev/ebay-deletions
Challenge Code Received from eBay: 6e90b9b9d8b1a23b95e54565212ed40274f1abc83f1a826ba612fdd16b8dec3f
Verification Token I Used: EbayTestTokenForProductionKeys2025
My Server's Correctly Generated Response Hash: {'challengeResponse': '/EVFhcRAXI/5dXamMpNg2tY83BWwTbqWVSecangfKH4='}
My Server's Response Code: 200 OK

I have already tried troubleshooting every possible issue on my end, including:

Fixing HTTP vs. HTTPS in the hash calculation.
Regenerating the verification token multiple times to rule out copy-paste errors.
Using a simple, hand-typed token (EbayTestTokenForProductionKeys2025).
Switching tunneling services (from ngrok to localhost.run) to rule out proxy issues.

The validation fails every single time, even though my logs show I am doing everything correctly. Given that the support button is also broken, this appears to be an issue with the eBay developer portal.

Could you please either manually approve my endpoint or have someone from your technical team investigate why the validation is failing? I am completely blocked from going live.

Thank you.

emmala_19

Posted 10 months ago·Last reply 10 months ago

3 comments

jongilbraith

·10 months ago

I think you've made it further than me!

I wasn't even able to pass the verification test so have for now gone the exemption route, but I will be wanting to use notifications so will have to return to it and work it out at some point.

jongilbraith

·10 months ago

I wasn't able to get my verification working either, though my produced hash using your details above doesn't match yours.

This is my ruby implementation.

❯ irb
irb(main):001> Digest::SHA256.hexdigest("6e90b9b9d8b1a23b95e54565212ed40274f1abc83f1a826ba612fdd16b8dec3fEbayTestTokenForProductionKeys2025https://unpeaceful-nonburnable-milda.ngrok-free.dev/ebay-deletions")
=> "3b8ec5c9c36b00ab6c73c9330a5f162f857413d259564aae097d3798432d2466"
irb(main):002>

If I use one of the examples in the docs with another language (addressing some errors I encountered trying to use them straight) I get the same output as my ruby.

❯ uv run python
Python 3.11.9 (main, Apr  2 2024, 08:25:04) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> challengeCode = "6e90b9b9d8b1a23b95e54565212ed40274f1abc83f1a826ba612fdd16b8dec3f"
>>> verificationToken = "EbayTestTokenForProductionKeys2025"
>>> endpoint = "https://unpeaceful-nonburnable-milda.ngrok-free.dev/ebay-deletions"
>>>
>>> string = challengeCode+verificationToken+endpoint
>>>
>>> import hashlib
>>> m = hashlib.sha256(string.encode(encoding = 'UTF-8', errors = 'strict'));
>>> print(m.hexdigest());
3b8ec5c9c36b00ab6c73c9330a5f162f857413d259564aae097d3798432d2466
>>>

emmala_19

OP10 months ago

You are exactly correct. The documentation is wrong. The code example is correct, and the text description is misleading. Ebay's server is expecting the raw hexadecimal digest string, not the base64 encoded version.

It finally saved, but now I hit another error:

"Notification delivery failed with HTTP status code 500 from https://unpeaceful-nonburnable-milda.ngrok-free.dev/ebay-deletions. Please ensure that the marketplace account deletion notification endpoint is ready to receive notifications."

The test notification does not render with ngrok or my backend until about 10 minutes later, which exceeds the timeout eBay has. If you know anything about resolving that, I'm all ears.

Appreciate the help!