# The v4 API is deprecated

name.com API deprecated /v4/* without giving a shutdown date yet.

The provider has deprecated the legacy v4 API without a shutdown date. Calls matching /v4/* will eventually fail, though they remain accessible during a transition period. All new development should target the newer platform rather than these legacy routes.

## What to use instead

Move to the name.com Core API following the migration guide. The transition requires more than updating an endpoint, including using JSON bodies with Content-Type: application/json and using UpdateDomain instead of the lock, autorenew, and WHOIS privacy actions.

- API: name.com API (api.name.com)
- Kind: Version retirement
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v4/*`
- Source: [Announcement](https://docs.name.com/guides/migration-guide)
- Verified: October 26, 2026, against name.com API's own pages
- Page: https://www.okapi.bot/providers/name-com-api/breaking-changes/the-v4-api-is-deprecated/

## name.com API's words

> While the legacy v4 API remains accessible during a transition period, all new development should use the name.com Core API (latest version recommended).

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent