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 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
-
How to remove bad or spammy links from Moz?
My website has gotten some bad and spammy links. I know how to disavow bad links from Google. But I reviewed Moz and haven't got any disavow option.
API | | juanitajb9
Have any disavow option on Moz? How can I remove the bad links from Moz? Thanks0 -
Mozscape API Updates (Non-updates!) - becoming a joke!
This is the 3rd month in succession where the Mozscape index has been delayed. Myself and clients are losing patience with this, as I am sure many others must be. Just what do you suppose we tell clients waiting for that data? We have incomplete and sometimes skewed metrics to report on, delays which then get delayed further, with nothing but the usual 'we are working on it' and 'bear with us'. It's becoming obvious you fudged the index update back in January (see discussion here with some kind of explanation finally from Rand: https://moz.com/community/q/is-everybody-seeing-da-pa-drops-after-last-moz-api-update), and seems you have been fumbling around ever since trying to fix it, with data all over the place, shifting DA scores and missing links from campaign data. Your developers should be working around the clock to fix this, because this is a big part of what you're selling in your service, and as SEO's and marketers we are relying on that data for client retention and satisfaction. Will you refund us all if we should lose clients over this?! .. I don't think so! With reports already sent out the beginning of the month with incomplete data, I told clients the index would refresh April 10th as informed from the API updates page, only to see it fudged again on day of release with the index being rolled back to previous. So again, I have to tell clients there will be more delays, ...with the uncertainty of IF it WILL EVEN get refreshed when you say it will. It's becoming a joke.. really!
API | | GregDixson2 -
Frequency of Moz page authority updates?
I have some new pages on my site, and Moz gives them a very low PA ranking. I am wondering if these scores are updated monthly or quarterly? I'm not sure how frequently to check back for updated scoring.
API | | AndrewMicek0 -
Connect to API
Hello Very often, when we connect to the API we get http error 401. We make some reconnections. How solve this problem? Request: https://lsapi.seomoz.com/linkscape/url-metrics/?AccessID={MY AccessID}&Expires=1478887421&Signature={MY Sig} Body: ["slemma.com"] Response: {
API | | SlemmaDev
"status" : "401",
"error_message" : "Permission denied: bjeacbehaehnbmhibjgnamekcheocbfcddeaci"
} Thanks!0 -
Can the API Filter Links with Certain Anchor Text?
I am trying to get all links that have a certain strings in their anchor text: I am using the python library: https://github.com/seomoz/SEOmozAPISamples/blob/master/python/lsapi.py Looking at the documentation, it says I can get the normalized anchor text by using the bit flag 8 for the LinkCols value: https://moz.com/help/guides/moz-api/mozscape/api-reference/link-metrics So I tried this: links = l.links('example.com', scope='page_to_domain', sort='domain_authority', filters=['external'], sourceCols = lsapi.UMCols.url, linkCols=8) But it doesn't return the expected 'lnt' response field or anything similar to the anchor text. How do I get the anchor text on the source URLs? I also tried 10 for the linkCols value, to get all the bit flags in the lf field as well as the anchor text. In both instances (and even with different variations of targetCols & sourceCols), this is all the fields that are returned: 'lrid', 'lsrc', 'luuu', 'uu', 'luupa', 'ltgt'
API | | nbyloff0 -
Keywords API
Does MOZ offer any statistics/data about keywords through the API? I didn't see anything in the documentation... Thanks! Justin
API | | Campaignium0 -
How much attention should I pay to Moz's DA/PA?
Hola! I've been optimising a site since October and our hard work has yielded a sizeable increase in organic traffic, revenue, quality, relevant links and Search Metrics scoring since commencing the campaign. After yesterday's Moz update, the DA has dropped slightly and a number of pages' PAs have dropped significantly (i.e. from 27 to 17). So here are my questions: My 'white hat' optimisation is clearly working. The site is enjoying more than 100% year-on-year increase in organic traffic and we're currently pulling in more organic visitors than ever before. Why is Moz's score not reflecting this? Some of the pages that have seen sizeable PA drops have had their URLs changed since the last Moz update. For example, I've optimised a URL from www.mysite.com/cases-covers to www.mysite.com/phone-cases to coincide with search volumes. I've added optimised content to this page too, but the PA has dipped from 27 to 17. A 301 redirect has been correctly added, and this is evident by a PA of 17 and not zero, which is what a brand new page would have. Am I paying too much attention to Moz's scores? It's a bit disheartening to see a drop after a lot of hard work. However, I guess the only thing that really counts is an increased volume of search traffic and revenue, right? Cheers, Lewis
API | | PeaSoupDigital0 -
What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?
Hi, I am not sure what this error message is: "Error.aspx?aspxerrorpath". It immediately follows pages that are given at 302 status in Moz's crawl report. The same pages have never had this error before: | http://www.homedestination.com/news/2013/Minneapolis-home-price-appreciation.html | | http://www.homedestination.com/mortgage-worksheet.html | | http://www.homedestination.com/foreclosure-eligibility.html | Each page has a 100% score with WC3. Could you give me more insight as to what Moz may suggest I do to give the page a 200 HTTP status as before? Thanks.
API | | jessential0