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 Mozscape API subscription
We have questions regarding our subscription and the plan we are on. We are more interested in Mozscape API and not the features that we have access to currently. Will you let us know how we can change. Is there some one that we can chat with. Thanks,
API | | PatientPop
Naveen
naveen.sarabu@patientpop.com0 -
Unsolved Does Anyone use DashThis API with MOZ?
Hi Team
API | | SkyrailCairns
Looking to share MOZ API credentials with DashThis - They provide an all in one reporting solution for all aspects of digital marketing.
Does anyone use DashThis?0 -
API url_metrics Error deserializing POST body
Getting error in https://lsapi.seomoz.com/v2/url_metrics API I'm using Basic Auth for authentication. { "name": "Bad Request", "message": "Error deserializing POST body"} CVW2T4f
API | | verdet32321 -
New Entry Level Mozscape API Plan
With the changes coming to our Free Mozscape access, and many of you asking for a lower priced API tier, we will now be offering an Entry Level plan. This plan will be priced at $250 per month for 120,000 rows of data, and $20 per 10,000 rows of overage. Here are some more details: Entry Level Mozscape API Access
API | | IanWatson
$250 - Per month
Overages:
$20 per additional 10,000 rows
Included Calls:
URL Metrics
Links
Top Pages
Anchor Text
Rows per Month:
120,000
Rate Limit:
200 requests per second The new Entry Level plan is not yet up on our Pricing Page, however if you are interested, reach out to me directly and I can help you get set up. Ian Watson - IanW@Moz.com6 -
10/14 Mozscape Index Update Details
Howdy gang, As you might have seen, we've finally been able to update the Mozscape index after many challenging technical problems in the last 40 days. However, this index has some unique qualities (most of them not ideal) that I should describe. First, this index still contains data crawled up to 100 days ago. We try to make sure that what we've crawled recently is stuff that we believe has been updated/changed, but there may be sites and pages that have changed significantly in that period that we didn't update (due to issues I've described here previously with our crawlers & schedulers). Second, many PA/DA and other metric scores will look very similar to the last index because we lost and had problems with some metrics in processing (and believe that much of what we calculated may have been erroneous). We're using metrics from the prior index (which had good correlations with Google, etc) until we can feel confident that the new ones we're calculating are correct. That should be finished by the next index, which, also, should be out much faster than this one (more on that below). Long story short on this one - if your link counts went up and you're seeing much better/new links pointing to you, but DA/PA remain unchanged, don't panic - that's due to problems on our end with calculations and will be remedied in the next index. Third - the good news is that we've found and fixed a vast array of issues (many of them hiding behind false problems we thought we had), and we now believe we'll be able to ship the next index with greater quality, greater speed, and better coverage. One thing we're now doing is taking every URL we've ever seen in Google's SERPs (via all our rank tracking, SERPscape, the corpus for the upcoming KW Explorer product, etc) and prioritizing them in Mozscape's crawl, so we expect to be matching what Google sees a bit more closely in future indices. My apologies for the delay in getting this post up - I was on a plane to London for Searchlove - should have got it up before I left.
API | | randfish4 -
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