- Shipped
- April 24, 2026 at 6:13 AM UTC
- Author
- Kamo
- Commit
- 8f9f5dc
GoDaddy now returns HTTP 400 with code=UNABLE_TO_AUTHENTICATE and body "Bad Request : Bad Request" when an account does not meet their current production Domain API eligibility (10+ domains on the account OR an active Discount Domain Club membership). The credentials can be perfect and the call still fails. Our client was rethrowing that as the raw "Bad Request" body, which is useless. - **************** now detects UNABLE_TO_AUTHENTICATE in the 400 body and raises a specific, actionable error explaining the GoDaddy eligibility gate. - Both the client's verifyCredentials and SubdomainBranchesController's PUT handler now sanitize the key and secret by stripping wrapping quotes, which commonly sneak in from "copy key" flows on the GoDaddy developer portal and produce the same 400.