Welcome to the Q&A Forum

I'm assuming that moz assign a unique internal id to each page, subdomain and root_domain. When making v2/links requests, are these moz-specific ids available? Currently, when gathering backlinks for a client we're generating our own ids. Maintaining uniqueness is costly time-wise.

"results": [{
            "source": {
                "page": "news.energysage.com/pros-cons-electric-water-heaters/",
                "subdomain": "news.energysage.com",
                "root_domain": "energysage.com",

...

"target": {
                "page": "mainlineplumbing.net.au/",
                "subdomain": "mainlineplumbing.net.au",
                "root_domain": "mainlineplumbing.net.au",

"Date First Seen","Date Last Seen" and "Date Lost"  are columns in the CSV exported from LinkExplorer's Inbound Links page. How do I get that data from the API?

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?

Ok, some specifics:

Today I downloaded moz-inbound-links-for-fordanddoonan_com_au-2019-05-07_06_29_56_307340Z.csv. I has a header as follows:

Inbound Links for fordanddoonan.com.au
Scope pld
Sorted by source_page_authority
Filters: external+not_deleted
Anchor text all
Source PLD all

What API scope matches the one given in the header namely "pld"?

Please also point me to the place in the documentation where a filter of "not_deleted" can be specified, as the header has "not_deleted" as a Filter attribute but I can't see that in any of the documentation.

I do need some hand-holding here. I'm trying to use the API to generate a moz-inbound-links report but I'm not at all sure where to start.

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
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.

So I've got this server-side JScript object I've declared which works nicely for us.

var mozObj = new MozInteraction()
.setMethod("GET")
.setHost("http://lsapi.seomoz.com")
.setPath("linkscape/url-metrics")
.setCols(parseInt("11111111111111111111111111111111111111111111111111111", 2))
.setLines(10)
.setAccessId(accessId)
.setSecret(secret)
.setExpires((new Date()).addDays(1).valueOf())
.generateSignature();

etc etc

The setCols call sets the Cols value to the maximum possible: 9007199254740991.

The weird thing is that in the JSON response I get a whole pile of column names that I can't find descriptions for in the documentation at https://moz.com/help/links-api/making-calls/response-fields

e.g.

ffspl1 ffspl2 ffspl3 ...  fuspl0 fuspl1 fuspl2 fuspl3 ...  pfspl0 pfspl1 pfspl2 pfspl3 ... puspl0 puspl1 puspl2 puspl3... etc