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



## Overview

The `v1` namespace exposes Domains operations that act on the domains owned by the authenticated account. Caller identity is established by the `Authorization` header alone; some operations also accept an `X-Shopper-Id` header to act on behalf of a specific shopper.

The `v1` namespace is account-scoped; use `v2` when you need async operation tracking (action queues, status polling, and notifications). 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 v1 namespace is available at [/openapi/domains-v1.json](https://developer.godaddy.com/openapi/domains-v1.json) — useful for code generation, SDK tooling, and LLM context.
</Callout>

## Operation groups

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

<Cards>
  <Card title="Find" description="Operations for searching availability and suggesting alternate names." href="/docs/references/rest/domains/v1/find-domains" />

  <Card title="Register and renew" description="Operations for searching availability, validating contacts, suggesting alternate names, retrieving registry agreements, and registering a domain." href="/docs/references/rest/domains/v1/register-and-renew-domains" />

  <Card title="Manage" description="Operations for listing the domains owned by the authenticated account, fetching detail for a single domain, updating contacts and registration settings, and cancelling a registration." href="/docs/references/rest/domains/v1/manage-domain-settings" />

  <Card title="DNS" description="Operations for reading, replacing, adding, and deleting DNS records on a domain managed by GoDaddy's authoritative nameservers." href="/docs/references/rest/domains/v1/manage-dns" />

  <Card title="Transfer" description="Operations for renewing a domain, initiating an inbound transfer, and verifying transfer email." href="/docs/references/rest/domains/v1/transfer-domains" />
</Cards>

## Authentication and scopes

Every v1 operation requires an `Authorization` header carrying a Personal Access Token (Bearer) or a legacy `sso-key` credential. PATs use the granular Domains & DNS scopes listed in [Authentication](https://developer.godaddy.com/docs/api-users/auth), like `domains.domain:read`, `domains.domain:update`, `domains.dns:update`, and `domains.transfer:execute`.

## 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) |
| Cursor-based pagination on `GET /v1/domains`    | [Pagination](https://developer.godaddy.com/docs/api-users/pagination)   |