Unknown data items in Links API response

[StevePoul]

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?

[meghanpahinui]

Hi there!

Thanks so much for the question! Sorry for the confusion here. The best thing to do regarding those blank fields would be to ignore them. These fields are not actually calculated but are returned as empty/default values. If you would like to see fewer of those fields, adjusting the TargetCols, LinkCols, and SourceCols is the best way to do that. However, some fields (lrid, lsrc, ltgt) are included in all responses regardless of the requested columns.

I hope this helps! If you have any other questions or need anything else, please do feel free to send an email on over to help@moz.com.