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 Issue with API Results and Excessive Token Consumption
-
Dear Moz Support Team,
I hope this message finds you well. I am writing to express my concerns regarding the performance of the Moz API, which I have been using for domain information retrieval through Zapier.
Despite paying for your API service, I am encountering several significant issues that are affecting my ability to use the service effectively:
Incorrect and Inconsistent Data: When I query domain information, I receive incorrect results for Page Authority (PA), Domain Authority (DA), and Spam Score (SS). Specifically, PA and DA are always returned as 1, while SS is consistently -1, which indicates that the data being provided is either incomplete or incorrect. This discrepancy is preventing me from relying on your service for accurate domain insights.
Excessive Token Consumption: I have noticed that the API token usage is significantly higher than expected. After querying only 250 domains, my token consumption has already exceeded 6,000 tokens, which seems unusually high. I had understood that the token usage would be calculated per query, but it appears that the consumption is much higher than anticipated.
Given that I have invested in this service, I am frustrated that I am not receiving the expected level of performance and data accuracy. Could you please investigate these issues and provide clarity on why this is happening? Additionally, I would appreciate any guidance on how to resolve these discrepancies and ensure that I am using the API in the most efficient way possible.
I look forward to your prompt response and assistance in resolving these issues. thank you
-
The problems you're encountering with incorrect metrics like PA, DA, and SS are indeed concerning. These values being consistently incorrect might suggest a technical glitch on Moz's end or a potential misconfiguration in the API integration with Zapier. It might be worth double-checking if the correct endpoint and parameters are being used in the queries.
Regarding excessive token consumption, the rate seems unusually high, especially for just 250 domains. This could be due to additional queries being made per domain (perhaps for related metrics) or an inefficiency in how the API calls are structured in your setup. Moz’s support team should clarify the token calculation method, as this doesn't align with typical expectations.
I'd recommend reaching out to Moz support directly and providing them with specific query examples and token logs to investigate further. In the meantime, it might help to review your website API usage patterns to ensure no redundant calls are being made.
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 Help with API Error: "Query Not Found" for a Specific URL
Hi everyone, I'm trying to retrieve data for a specific URL using the Moz API, specifically the data.site.metrics.fetch method. The URL I'm querying is: https://www.fiftyfiveandfive.com/ai-agents-marketings-new-means-of-production When I make the API request, I receive the following 404 error: { "id": "unique-id-testing", "jsonrpc": "2.0", "error": { "code": -32655, "status": 404, "data": { "key": "site_query.query", "value": "https://www.fiftyfiveandfive.com/ai-agents-marketings-new-means-of-production" }, "message": "That query was not found." } } However, when I check the URL in Moz Link Explorer, I can see that the page has a Page Authority of 23 and a Domain Authority of 36, but no backlinks or ranking keywords. What I'm Trying to Achieve:
API | | Chris_Wright1664
I’m attempting to retrieve metrics for this page via the API, but it seems like the API does not recognise the URL, even though it’s visible in Link Explorer. Questions: Why does the API return "Query Not Found" for a URL that is indexed in Link Explorer? Is there a way to request Moz to crawl or re-crawl this URL to ensure it's accessible via the API? Are there any additional criteria the API requires (e.g., backlinks, ranking keywords) before it recognises a URL? Additional Info: I’ve verified that my robots.txt file allows all bots, including Rogerbot. list itemThe page is included in the sitemap, and the URL is accessible without any restrictions. list itemI’d appreciate any insights on how to resolve this issue or steps to take so that the Moz API can retrieve data for this URL.0 -
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 How to get Domain Authority using API ?
I wanted to test the API and while looking on the documentation urls, I cannot find details on how to get Domain Authority. is that not available to query ? was it replaced by Brand Authority ? is it only available for the paid API or for the free one too ? I looked at many documentation pages but I find it very confusing and frustrating, there are many versions of the documentation and various URLs and not clearly labeled, I understand some are V1, V2, V3, etc, but I didn't find sample API calls for Domain Authority. Thank you.
API | | adrianTNT0 -
Solved Payment Issue in Subscription Upgrade
Hi, I’m trying to upgrade from the Starter to the Standard plan, but I keep encountering an error: "Failed to send subscription update to Stripe." Could you please assist me in making the switch?
Product Support | | Devesh_Chauhan0 -
Unsolved Generate an Access ID and API key
Hello, I can't generate an Access ID and API key for my account.
API | | OlegShavilov
I need a Links API and I'm ready to buy a paid subscription, but I can't do it. Link https://cloudz.click/products/mozscape/access
Redirected to https://cloudz.click/api/dashboard And i dont see any options for create Access ID0 -
Unsolved MOZ API to Google Data Studio
Dopes MOZ have anything like this? https://www.semrush.com/features/google-data-studio-connector/
Product Support | | WebMarkets0 -
Unsolved Can I get Moz keywords via API?
Hi, my boss is asking if you "have any API for keyword research -- e.g., as soon as a user creates a card title in [our application], we can auto-recommend keywords from Moz within [the application]. I shared a link with him to your Links API page, but he says he doesn't think that API does the above. Can you help? Thank you, Renae
API | | CarolinaRen0 -
Unsolved url_metrics - Error deserializing POST body
Hi, I'm trying to reproduce this Postman url_metrics request in Google Apps Script (GAS) : moz forum 2-2.jpg But in GAS, I get this error : moz-forum 2.jpg I suspect it's the body (line 90) that causes the issue, but can't figure out how to fix it. Any suggestion ?
API | | adalako0
