/linkscape/* → version retirement
Moz Links APIDeprecated, no date
The provider deprecated the legacy Links API V1 without a shutdown date. This deprecation affects all requests to lsapi.seomoz.com on the /linkscape/* endpoints. Calls to these legacy endpoints fail.
Calls it hits
/linkscape/*
What to use instead of these calls
Switch to the current Moz API using POST api.moz.com/jsonrpc, such as the data.site.metrics.fetch call. Moving to the replacement requires more than changing an identifier, as it requires a separate Moz API token and a JSON-RPC request format.
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 /linkscape/* 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
/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.