November 16, 2026: The Domain Valuation API now has a v2 endpoint with a simpler response

View as Markdown
November 16, 2026API
Valuation API
New

You can now get a GoValue valuation from GET /v2/domains/domain-names/{domain-name}/govalue, a new endpoint that takes the domain in the path and returns a smaller, standard response. We recommend it for new integrations.

What changed

A new endpoint is available:

  • GET /v2/domains/domain-names/{domain-name}/govalue: returns the GoValue for the domain in the path.

It differs from GET /v1/domains/govalues in four ways:

  • It requires a Personal Access Token with the domains.domain:read scope from an account that has a GoValue subscription. It doesn't accept the legacy sso-key credential.
  • The response contains domainName, goValue, maxDailyUsage, and dailyUsage. It omits status, goValueWholesale, listPrice, minPrice, maxPrice, and the salesProbability fields.
  • goValue.value is a whole number of dollars (USD), so 1234 means $1,234.
  • Errors use the shared GoDaddy error body with name, correlationId, and message.

Internationalized domain names aren't supported. A punycode name like xn--80ak6aa92e.com returns 400.

Who is affected

New integrations choosing between the two versions, and developers who want a response without the pricing and probability fields. Integrations that call GET /v1/domains/govalues keep working, and that endpoint stays available. Both versions need an active GoValue subscription.

Last updated on

How is this guide?

On this page