Unsolved Regarding Moz API token password update
-
Hi,
In March we have updated password for MOZ API and used in our application it worked, but currently the updated password is not working and in the MOZ site the old password is shown and its active. We are using Legacy username and password.
We see that 5 tokens can be added for API, if we add 2 tokens both will be active.
We are currently using free services.Please help us resolve this issue.
-
@emma-bahlke Hello Emma, We haven't received any reply for our comment. If we are using the newly created secret ID/ token, the API is not getting called and we are not receiving the count value for the backlinks.
-
@emma-bahlke Good Morning, Can you provide any suggestion on the reply given?? Thanks
-
@emma-bahlke Good Morning, Can you provide any suggestion on the reply given?? Thanks
-
@emma-bahlke Yes, we are using in the form of Legacy ID/ Secret Key. The old one is working, but the newly created one is not working in our code.
-
@emma-bahlke We are using it in the form of Access ID and Secret. Even then, it is not showing any backlinks for our application.
-
@emma-bahlke Wanted to follow up on the reply,
Yes, we were able to add a new token. But when we try to use the new token, It's not connecting/returning the backlinks count for our application. We are skeptical to delete the old one as our Production application is using it.Please let us know if you need anymore information.
-
@NickAndrews Sorry for the late reply! Is there a particular error message you're receiving, and can you share the code you're using with the new token? With the new tokens, you can do one of two things:
- Use it in its token form by providing it in the custom x-moz-token header
- Use it in the legacy access ID/secret key form by clicking "Show legacy credentials" to the right of the token and providing those via basic auth, which is how your existing API integration will work
Is it possible you're using the token form (the single long string value which is shown by default in each row of tokens on the dashboard) and providing it via basic auth, or vice versa?
-
@emma-bahlke Yes, we were able to add a new token. But when we try to use the new token, It's not connecting/returning the backlinks count for our application. We are skeptical to delete the old one as our Production application is using it.
-
@NickAndrews Hi Nick, are you able to add a new token and delete the old one? You can delete the old one by hitting the trash icon next to it on the Moz API dashboard: https://moz.com/help/links-api/getting-started/usage-dashboard
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
-
Unsolved Api limits on free plan
Good afternoon. I tried connecting free access to api https://moz.com/help/links-api/v1-archive/v1-free-api-access to retrieve DA data. After several requests to the api I got a message: "Your monthly row limit reached" Can you tell me what this error is related to? Or Moz doesn't have free api access anymore?
API | | Dima124dsfg1 -
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 -
Moz got problem crawling SquareSpace websites?
Moz sent us an email about our website https://www.openhill.com that they failed to crawl. I checked the forums with the same issues with mine and it looks like that Moz has problems with websites from Squarespace. I wonder if you do have a workaround on this. Let me know if you have instructions for me to fix this kind of issue. Thanks!
API | | leahdickey0 -
Mozscape Index update frequency problems?
I'm new to Moz, only a member for a couple months now. But I already rely heavily on the mozscape index data for link building, as I'm sure many people do. I've been waiting for the latest update (due today after delay), but am not seeing any mention of the data yet - does it normally get added later in the day? I'm not that impatient that I can't wait until later today or tomorrow for this index update, but what I am curious about is whether Moz is struggling to keep up, and if updates will continue to get more and more rare? For example, in 2013 I count 28 index updates. In 2014 that number dropped to 14 updates (50% drop). In 2015, there was only 8 (another 43% drop), and so far this year (until the March 2nd update is posted) there has only been 1. This isn't just a complaint about updates, I'm hoping to get input from some of the more experienced Moz customers to better understand (with the exception of the catastrophic drive failure) the challenges that Moz is facing and what the future may hold for update frequency.
API | | kevin.kembel1 -
Two days since the supposed update
And still no update. Less a question, more a comment. Feeling a bit of deja vu here.
API | | pfrance3 -
API - Row Limit Question
Hi, I'm new to using Moz, and have just got a "Low volume" API account set up. My question is, because ive not yet reached my maximum "Rows per month" limit, what behaviour happens when i reach it? Do i get an error code, if so what, and whats the status code. If not, does my account keep downloading the rows and i get charged extra (in accordance with the cost of the additional rows)? Or is the whole additional rows think like a bolt on? Basically i want to make sure i dont get charged extra each month, and i need the status code returned to handled this in my app. I couldnt see anything explicit in the documents. Cheers
API | | MattHopkins0 -
3 result limit to Top Pages API call
I am using the MOZ API to make calls for the top pages for a particular URL. However, when I pass in any limit value greater than 3 the API only returns 3 results. I have even tried to put in URLs like 'www.moz.com' and still only 3 results. Sample call to the API below: http://lsapi.seomoz.com/linkscape/top-pages/www.moz.com?AccessID=member-xxxxxxxxx&Expires=1419020831&Signature=xxxxxxxxx&Cols=2052&Offset=0&Limit=50
API | | solodev0