{"slug":"name-com-api","name":"name.com API","host":"api.name.com","site":"https://name.com","category":"cloud","docsUrl":null,"sources":[{"kind":"changelog","url":"https://docs.name.com/"},{"kind":"archive","url":"https://docs.name.com/guides/migration-guide"}],"url":"https://www.okapi.bot/providers/name-com-api/","json":"https://www.okapi.bot/api/v1/providers/name-com-api.json","breakingChanges":[{"slug":"the-v4-api-is-deprecated","api":"name-com-api","title":"The v4 API is deprecated","kind":"version_retirement","outcome":"fails","model":null,"announcedAt":null,"effectiveAt":null,"scope":null,"calls":["/v4/*"],"method":null,"path":"/v4/*","source":{"url":"https://docs.name.com/guides/migration-guide","kind":"archive"},"quote":"While the legacy v4 API remains accessible during a transition period, all new development should use the name.com Core API (latest version recommended).","migration":"Move to the name.com Core API (https://api.name.com/core/v1/...), following the v4 to Core API migration guide: JSON bodies with Content-Type: application/json, UpdateDomain instead of the lock, autorenew and WHOIS privacy actions.","migrationChange":null,"needsDecision":null,"text":{"summary":"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.","migration":"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.","by":"writer"},"publishedAt":"2026-10-23T10:07:31.543Z","updatedAt":"2026-10-25T21:34:40.927Z","status":"deprecated","tone":"deprecated","url":"https://www.okapi.bot/providers/name-com-api/breaking-changes/the-v4-api-is-deprecated/"}]}