Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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 MOZ API for domain authority
I am using the MOZ API to check domain authority (DA). Recently, I noticed a discrepancy: the DA value retrieved via the API differs from the result on the MOZ homepage. Specifically, the API returns a DA of 10, while the homepage shows "NO DATA." Additionally, other services like Ahrefs report a DA of 0. I relied on the MOZ API's result when purchasing this domain and now feel misled. I would like to understand the exact reason for this inconsistency.
API | | Skys0 -
Unsolved Moz API returning incorrect PA data
So I've been attempting to figure out Moz API to allow for batches of URLs to be searched and the data to be nicely put into a google sheet. I've setup the MOZ API for sheets add-on and everything appears to work, but after spot checking some of my data, I've found that for some reason, the page authority data returned by Moz API appears to be way off the actual number presented by other Moz tools, such as the tool bar and main site.
API | | willadogy
Screenshot 2023-06-01 at 9.38.25 AM.png
Screenshot 2023-06-01 at 9.41.43 AM.png As you can see, in this one example off my list, the returned PA value is 6 points lower than the value returned from the Moz tool bar and website analysis.
If the data returned is incorrect, how is Moz API useful? Am I missing something? Would love some help or advice, as this tool would be very useful in a functioning state!0 -
Moz not working properly
I'm using MOZ BAR extension . It's not working properly on this https://brokescholar.com Can anyone tell me that is it/not showing da...
API | | sathoiue80 -
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 -
Seo moz api request problem [401 error_message Your authentication failed]
Hello Team, I have moz pro account. I'm getting following error for seomoz call using your API: {"status":"401","error_message":"Your authentication failed. Check your authentication details and try again. For more information on signed authentication, see: http://apiwiki.moz.com/signed-authentication"} The link that we are using is:
API | | eBrandz
http://lsapi.seomoz.com/linkscape/url-metrics/ And following bits are requested during the call: 68719476736 34359738368 32 2048 16384 The error is intermittent. It comes and goes. There were no issues with results 3 days ago. I suddenly started getting this error. Could you please investigate into it and let me know the cause of issues and its correctiveness. It will great if you can provide us a support email Id for immediate response. Thanks,0
