October 8, 2026: The Domains API now supports setting auto-renew and transfer-lock via POST /v3/domains/domain-names/{domain-name}/auto-renew and /transfer-lock

We've added two endpoints to Domains v3 so you can turn auto-renew and transfer lock on or off for a domain without going through v1 or v2.

What changed

Two new endpoints are available:

• POST /v3/domains/domain-names/{domain-name}/auto-renew — sets the auto-renewal preference. When enabled, the domain renews automatically before expiration using the payment method on file.
• POST /v3/domains/domain-names/{domain-name}/transfer-lock — sets the transfer lock (also known as registrar lock). Disabling it is typically a prerequisite for an outbound transfer.

Both accept a plain boolean request body and return 202 Accepted with a pollable DomainOperation, the same pattern as other v3 write operations. Both require the domains.domain:update OAuth scope.

Calling either endpoint when the domain isn't ACTIVE (for example PENDING_TRANSFER, HELD_REGISTRAR, or EXPIRED), or when the requested state already matches the current setting, returns 422.

Who is affected

Any developer managing domain settings on the Domains API. Existing v1 and v2 auto-renew and transfer-lock operations are unaffected; these v3 endpoints are additive.

Links

• Set auto-renew setting for a domain reference — endpoint schema
• Set transfer-lock setting for a domain reference — endpoint schema
• Domains v3 API reference — full v3 reference

Last updated on