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 -
How to cost is calculated in Moz API for fetching only backlinks
I am unable to understand which particular API used to get the backlinks. And how cost is calculated. Suppose I Hit the API one time it gave me 100 backlinks of a particular domain. Does that mean i used 100 rows?
API | | maxfun00070 -
Paid access to the API
Hi!
API | | SlemmaDev
We paid for the trial period, but we don't have access to the API (Anchor-Text Metrics, and to the other paid URL Metrics). Why? Thanks!0 -
September's Mozscape Update Broke; We're Building a New Index
Hey gang, I hate to write to you all again with more bad news, but such is life. Our big data team produced an index this week but, upon analysis, found that our crawlers had encountered a massive number of non-200 URLs, which meant this index was not only smaller, but also weirdly biased. PA and DA scores were way off, coverage of the right URLs went haywire, and our metrics that we use to gauge quality told us this index simply was not good enough to launch. Thus, we're in the process of rebuilding an index as fast as possible, but this takes, at minimum 19-20 days, and may take as long as 30 days. This sucks. There's no excuse. We need to do better and we owe all of you and all of the folks who use Mozscape better, more reliable updates. I'm embarassed and so is the team. We all want to deliver the best product, but continue to find problems we didn't account for, and have to go back and build systems in our software to look for them. In the spirit of transparency (not as an excuse), the problem appears to be a large number of new subdomains that found their way into our crawlers and exposed us to issues fetching robots.txt files that timed out and stalled our crawlers. In addition, some new portions of the link graph we crawled exposed us to websites/pages that we need to find ways to exclude, as these abuse our metrics for prioritizing crawls (aka PageRank, much like Google, but they're obviously much more sophisticated and experienced with this) and bias us to junky stuff which keeps us from getting to the good stuff we need. We have dozens of ideas to fix this, and we've managed to fix problems like this in the past (prior issues like .cn domains overwhelming our index, link wheels and webspam holes, etc plagued us and have been addressed, but every couple indices it seems we face a new challenge like this). Our biggest issue is one of monitoring and processing times. We don't see what's in a web index until it's finished processing, which means we don't know if we're building a good index until it's done. It's a lot of work to re-build the processing system so there can be visibility at checkpoints, but that appears to be necessary right now. Unfortunately, it takes time away from building the new, realtime version of our index (which is what we really want to finish and launch!). Such is the frustration of trying to tweak an old system while simultaneously working on a new, better one. Tradeoffs have to be made. For now, we're prioritizing fixing the old Mozscape system, getting a new index out as soon as possible, and then working to improve visibility and our crawl rules. I'm happy to answer any and all questions, and you have my deep, regretful apologies for once again letting you down. We will continue to do everything in our power to improve and fix these ongoing problems.
API | | randfish11 -
Integrate Piwik data with Moz instead of Google Analytics?
Hello everyone, The company I work for had Google Analytics for all of our websites, dating back at least 4 years. Because of our email infrastructure, we accessed Analytics through a temporary account. Now this account worked fine for 4 years, until over the last two weeks where at some point Google deleted that account, and the Analytics connected to it. I've had no response from Google regarding this, but that's by the by. Anyway, I've made the decision to bring the analytics in house and hold the data ourselves. I've chosen Piwik for this, and it's been running fine for the last few days. However, I know Moz integrates with Google Analytics, but at the moment this is useless to me. Is there a way, or are there any plans, to integrate Piwik with Moz? If not, what benefits will I lose if I discontinue using Google Analytics with Moz?
API | | theponyclub0 -
About Expiry of MOZ API authentication and MOZ API call in .NET application
MOZ API signed authentication is getting expire after particular time, and coming up with the error "Authentication has expired , Re-send your authentication". **right now we are getting new authentication details using ** https://moz.com/products/api/keys after doing login. but, how do we get new credentials (authentication details) , by doing MOZ API call using c# or any other programming language, we are using this API in .NET. Also, How we can increase the session expiry time. i think it is concerned with the Sample Expires of Signed authentication , but we are unable to change it , as it is coming with the authentication failed.
API | | BenuAggarwal0 -
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