# Domains v2 (https://developer.godaddy.com/en/docs/references/rest/domains/v2)



## Overview

The `v2` namespace extends the Domains API with async operation tracking — action queues, status polling, and lifecycle notifications. Operation paths follow `/v2/customers/{customerId}/domains/...`.

Use `v2` when you need to track long-running writes (transfers, redemptions) that return `202 Accepted` instead of completing synchronously. For a task-shaped guide layered on top of these endpoints, see [Use the API → Domains](https://developer.godaddy.com/docs/api-users/manage-domains).

<Callout type="info" title="Machine-readable spec">
  The complete OpenAPI spec for the v2 namespace is available at [/openapi/domains-v2.json](https://developer.godaddy.com/openapi/domains-v2.json) — useful for code generation, SDK tooling, and LLM context.
</Callout>

## Operation groups

The v2 namespace is organized into seven operation groups, each rendered on its own reference page below.

<Cards>
  <Card title="Registration" description="Operations for registering a domain on behalf of a customer, including contact validation, schema retrieval, and registry-usage reporting." href="/docs/references/rest/domains/v2/register-domains" />

  <Card title="Management" description="Operations for retrieving a domain, updating its nameservers, renewing it, and redeeming it from grace period." href="/docs/references/rest/domains/v2/manage-domain-settings" />

  <Card title="Transfer" description="Operations for inbound and outbound transfers, including accept, reject, restart, and change-of-registrant flows." href="/docs/references/rest/domains/v2/transfer-domains" />

  <Card title="Forwarding" description="Operations for creating, updating, listing, and deleting HTTP forwarding rules on a domain, including privacy-side forwarding." href="/docs/references/rest/domains/v2/manage-domain-settings" />

  <Card title="Actions" description="Operations for tracking the status of asynchronous writes returned with 202 Accepted, including listing, fetching by type, and cancellation." href="/docs/references/rest/domains/v2/domain-actions" />

  <Card title="Notifications" description="Operations for subscribing to, retrieving, and acknowledging domain lifecycle notifications, plus their payload schemas." href="/docs/references/rest/domains/v2/domain-notifications" />
</Cards>

## Authentication and scopes

Every v2 operation requires an `Authorization` header carrying a Personal Access Token (Bearer) or a legacy `sso-key` credential. The principal must additionally be authorized for the customer named in the URL. PATs use the granular Domains & DNS scopes listed in [Authentication](https://developer.godaddy.com/docs/api-users/auth), such as `domains.domain:read`, `domains.domain:update`, and `domains.transfer:execute`.

## v2-only capabilities

Some operations have no v1 equivalent and must be reached through `v2`:

* **Domain forwarding** (HTTP redirects on a domain).
* **Notification subscriptions** (lifecycle events delivered to a callback or pulled on demand).
* **Customer-scoped change-of-registrant** (managed across customer boundaries).

## Conventions

| Concern                                              | Where it's documented                                                |
| ---------------------------------------------------- | -------------------------------------------------------------------- |
| Error envelope and retry semantics                   | [Errors](https://developer.godaddy.com/docs/api-users/errors)                                     |
| Rate limits (60 requests/minute per credential)      | [Rate limits](https://developer.godaddy.com/docs/api-users/rate-limits)                           |
| Asynchronous-write polling via the `Action` resource | [Actions reference](https://developer.godaddy.com/docs/references/rest/domains/v2/domain-actions) |