The OAuth 2.0 user-consent (3-legged) authorize endpoint
PROBLEM: The OAuth 2.0 user-consent (3-legged) authorize endpoint https://auth.ebay.com/oauth2/authorize?client_id= [auth.ebay.com]&response_type=code&redirect_uri=&scope=returns HTTP 500 with the following response for ALL scope combinations(sell.inventory, basic api_scope, commerce.identity.readonly, etc.): { "error_id": "temporarily_unavailable", "error_description": "The authorization server is currently unable to handle the request.", "http_status_code": 500 } Last verified failing: 2026-05-17 01:30 CEST (HTTP 500 response via curl).Continuously broken since approximately 2026-05-15 22:00 CEST — that is~36 hours and counting. Has not resolved itself. WHAT WORKS (credentials are valid): * Client Credentials grant — token endpoint POST https://api.ebay.com/identity/v1/oauth2/token [api.ebay.com] grant_type=client_credentials returns valid access_token HTTP 200 (verified live 2026-05-17 01:30 CEST). * GDPR Marketplace Account Deletion endpoint https://booking.uwe-uli-restaurant.de/ebay/account-deletion?challenge_code= [booking.uwe-uli-restaurant.de] returns HTTP 200 with valid SHA256 challengeResponse. Configuration in Developer Portal shows COMPLETE / VERIFIED. WHAT FAILS: The user-consent 3-legged OAuth flow. Without this endpoint we cannot obtain a user access token to use the SellAPIs (sell.inventory, sell.account, sell.fulfillment). The entire sellingintegration is blocked. REQUEST: Please investigate / reset the OAuth authorize backend for this specificApp-ID. We have already verified:- App-ID and Cert-ID are valid (client_credentials grant works)- RuName is correctly configured in Developer Portal- Account Deletion compliance is GREEN- App status in Developer Portal is "Production" Repro is one curl call away — happy to provide on request.
