/v4/* → version retirement
name.com API
Deprecated, no date
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.
Calls it hits
/v4/*
What to use instead of these calls
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.
In 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).
Facts
- API
- name.com API
api.name.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against name.com API's own pages
Questions
When does this change take effect?
name.com API deprecated /v4/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: name.com API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.