API url_metrics Error deserializing POST body
-
Getting error in https://lsapi.seomoz.com/v2/url_metrics API
I'm using Basic Auth for authentication.
{ "name": "Bad Request", "message": "Error deserializing POST body"}
-
Hi - thanks for reaching out to us.
In Postman, if you click on raw instead of form-data in Body, you can get results using the syntax found here: https://moz.com/help/links-api/making-calls/url-metrics. In your example, you could write:
{
"targets":["facebook.com"]
}
This should successfully return results for you. If you continue to run into issues, I would suggest reaching out to support at help@moz.com.
thanks!
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Unknown data items in Links API response
So I'm on the documentation page at https://moz.com/help/links-api/making-calls/url-metrics . I've copied the bit fields table into a spreadsheet. I've removed all the "deprecated" items and have totalled up the remaining items making a Cols= value of 182537205900657000. For want of better knowledge, I've used that same value for LinkCols=, SourceCols= and TargetCols=. The request url ends up being (anonymized): http://lsapi.seomoz.com/linkscape/links/fordanddoonan.com.au?Cols=182537205900657000&AccessID=xxx&Expires=1557458487346&Signature=xxx&SourceCols=182537205900657000&TargetCols=182537205900657000&LinkCols=182537205900657000&Limit=1000&Scope=page_to_domain&Filter=external My question is, what do I make of all the extra fields that I get in the json packet what should I do to remove them? These extra fields are: lrid, lsrc, ltgt, luufq, luueid, lufeid, luujid, luumrp, luumrr, luflan, lufspf, lufsplc, lufspp, lufsps, lufspsc, luus, lufuid, lupuid, lufipl, luupa, lupda, luued, lufed, luped, lupib, luulc, flan, fspf, fsplc, fspp, fsps Is it simply a case of limiting the values of TargetCols, LinkCols and SourceCols? If so, to what?
API | | StevePoul1 -
Can the API give the same data as the UI?
What I mean is, I'm not that interested in counts. What I'd like to figure out is how to get the API to give me what the UI gives me , so that for a given target domain I can download a report with the following fields: URL
API | | StevePoul
Title
Anchor Text
Spam Score
PA
DA
Linking Domains to Page
Target URL
Link Type
Link State
Date First Seen
Date Last Seen
Date Lost
HTTP Status Code
Links to Page
Outbound Domains from Page
Outbound Links from Page
Operator profile That's essentially the same as a CSV report generated by clicking on the "Export CSV" button. I could ,I suppose, get someone to write something in Selenium to enter a domain, click on the button and hang around on the notifications page for the results but I'd really rather not.1 -
MOZ API - Search Visibility
Hello there, We are looking to see if we can recreate the Search Visibility report through the API. We are wondering which API parameters and metrics we should use to recreate the report? Also, we want to distinguish between traffic coming from desktops and mobile traffic. Is this possible with the API? Which type of account do we need to use for these functionalities: the free account or paid account? We are currently using a free account. Also: we are wondering if can access historical data with the API? For instance: we want to determine the domain authority from October 2016 off on. Is this possible? Thanks in advance! Kind regards, Bart Minten
API | | thomas.deruiter0 -
Moz crawl error? DA & Linking domains significant drop.
Hi guys! Our site www.carwow.co.uk appears to have been punched in the face by the latest Moz update. It's claiming our #linking root domains has dropped from 225 to 135 and has subsequently hit our DA from 38 to 35. We haven't disavowed any links and our off-site strategy has been going well the past 2 months. Search performance has increased by around 15% (around 5k sessions) and rankings have improved week on week. Any idea if this is a Moz error? That's almost a 50% drop in linking root domains. Thanks, James
API | | Matt.Carwow0 -
Any idea why HubSpot (which uses the MOZ api) can find our backlinks but OSE can not?
Links are showing up in the HubSpot link tool within a couple of days. OSE has our site showing zero backlinks. ahrefs is finding them too but that makes more sense. Does the API update more frequently than OSE? Any thoughts? Thanks!
API | | KLEANTreatmentCenter0 -
Moz Analaytics: What does this error mean? analyze_page_issues.crawl_error.name
The new Moz Analytics are terrific. However, I don't know what this error means. Could anyone offer me further insights? Thanks,
API | | jessential0 -
How to pull metrics from API for a top 100 list
I'm working on a top 100 list for my industry and need a way to pull DA for the list of blogs and then sort them in descending order until it can pull other metrics (Alexa and follower count). Right now I am doing the above manually and was trying to hunt for a way for the table to update on a set date. any help / guidance appreciated
API | | ArfanB0 -
Huge in crease in on page errors
Hi guys I’ve just checked my online campaign and I see errors in my crawl diagnostics have almost doubled from the 21<sup>st</sup> of October to the 25<sup>th</sup> of October going from 6708 errors to 11 599. Can anyone tell me what may have caused this? Also I notice we have a lot of issues with duplicate page titles which seems strange as no new pages have been added, can anyone explain why this might be? I look forward to hearing from you
API | | Hardley1110
