/v3* → version retirement
restcountries.com
Deprecated, no date
The provider has deprecated the /v3* endpoints without a shutdown date. Affected calls will fail. Earlier iterations v1 through v4 were public iterations and have been deprecated in favor of later stable releases.
Calls it hits
/v3*
What to use instead of these calls
Move v3 and v3.1 calls to the v5 service, such as /countries/v5/names.common/{name}, passing an API key in an Authorization Bearer header. The move requires more than changing an identifier, as field names changed in v5 and accessing v5 requires choosing an account tier to obtain an API key.
v5 needs an account and an API key (free tier, paid plans above it).
In restcountries.com's words
The Countries API is currently at v5 , the first version we consider long-term stable ; versions v1 – v4 were public iterations and have been deprecated.
Facts
- API
- restcountries.com
restcountries.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against restcountries.com's own pages
Questions
When does this change take effect?
restcountries.com deprecated /v3* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: restcountries.com 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.
More from restcountries.com 1
-
No date
/v2/*Version retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.