/v2/* → version retirement
Moz Links APIDeprecated, no date
Moz Links API has deprecated /v2/* endpoints without a shutdown date. Calls made to these endpoints will eventually fail. The provider notes that documentation for V2 applies only to legacy versions rather than the current Moz API.
Calls it hits
/v2/*
What to use instead of these calls
Move to the current Moz API using calls like POST api.moz.com/jsonrpc with methods such as data.site.metrics.fetch. Transitioning requires more than updating an identifier, as the current Moz API requires its own API token and a JSON-RPC request shape.
The current Moz API takes its own API token and a JSON-RPC request shape.
In Moz Links API's words
Please note: The documentation found here is for the legacy Moz API V1 and V2 only. Our updated documentation for the current version of the Moz API can be found
Facts
- API
- Moz Links API
lsapi.seomoz.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Moz Links API's own pages
Questions
When does this change take effect?
Moz Links API deprecated /v2/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Moz Links 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.
More from Moz Links API 1
-
No date
/linkscape/*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.