Moz provides SEO data and analytics, including Domain Authority, Page Authority, and Brand Authority, link and linking-domain data, anchor text, ranking keywords, keyword metrics, and search engine results pages. The Moz API connector reads this data from the Moz API with an API token. Most templates use Moz row quota; a few, such as quota lookup and the global top pages and domains lists, are free.
Power end-to-end data operations for your Moz API API with Nexla. Our bi-directional Moz API connector is purpose-built for Moz API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Moz API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Moz API workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Moz API with a Moz API token, which it sends in the x-moz-token request header. The same token also works for the two legacy Links API v2 templates. Moz's older Access ID and Secret Key (Basic authentication) are not used by this connector.
Sign up for a Moz API plan, or sign in to your existing Moz API account. The free plan includes 50 rows of quota per month and requires a valid credit card; Moz does not charge the card unless you upgrade.
Open the Moz API dashboard, and click + Add Token to create an API token. An account can have up to five active tokens.
Most Moz API methods use rows from your plan's monthly quota, usually one row for each result returned. The free plan has 50 rows per month, so a single run of a list template can use up a large share of it. Paid plans include more rows, and whether usage beyond your allowance is billed as overage depends on your plan. The quota usage section below lists the cost of each template. Use the free Get Quota template to check your remaining rows and whether overages are enabled.
Repeated authentication failures
Moz blocks the calling IP address for 30 minutes after ten 401 or 403 responses within 5 minutes; a 403 includes running out of quota. If a credential test or flow fails with one of these errors, fix the token or quota before retrying. See Moz's error handling guide for details.
Moz API token, sent as the x-moz-token header. Create one on the Moz API dashboard (moz.com/api/dashboard > + Add Token). The connection test calls quota.lookup, which uses no quota.
Field
Required
Secret
Description
API Token
Yes
Yes
Moz API token from the Moz API dashboard (moz.com/api/dashboard > + Add Token). The same token works for the current Moz API and the legacy Links API v2.
To create a new Moz API credential, after selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Moz API
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
In the API Token field, enter the API token you created on the Moz API dashboard.
The API token is sensitive and should be kept secure. If it is exposed, delete it on the Moz API dashboard, create a new token, and update this credential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
Nexla tests the credential by calling the Moz quota.lookup method, which uses no quota.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Moz API connector tile from the list of available connectors, then select the credential that will be used to connect to your Moz account, and click Next; or, create a new Moz API credential for use in this flow.
Moz charges rows from your data quota (api.limits.data.rows) unless noted otherwise. Templates that return a list fetch a single page per run and charge for each result on that page, so their Max Results setting caps the cost of a run. Each scheduled run calls Moz again and uses quota again.
Template
Cost per run
Get Quota, Get Index ID, List Global Top Pages, List Global Top Domains
Free
List Locales
Free (zero rows), but the account must have row quota
Get Site Metrics, Get Brand Authority, Get Site Metrics Distributions, Get Final Redirect Target, Get Link Status, Count Ranking Keywords
1 row
Get Keyword Difficulty, Get Keyword Volume, Get Keyword Organic CTR, Get Keyword Priority, Get Keyword Search Intent
1 row
Get Keyword Metrics
Up to 4 rows (1 per metric with a value)
Get Keyword Metrics (Multiple)
Up to 5 rows per keyword
Get SERP
15 rows, less 1 per metric without a value
Get Site Metrics (Multiple), Get Site Metric History, Get Link Status (Multiple)
1 row per site, history item, or pair returned
List Top Pages, List Links, List Links From Domain, List Links By Anchor Text, List Linking Domains, List Recently Gained Linking Domains, List Recently Lost Linking Domains, List Anchor Text, List Ranking Keywords, List Keyword Suggestions
1 row per result returned
Get Link Intersect
N rows per result, where N is the number of sites in both lists
List Site Competitors
Links API (mozscape) quota: 50 units reserved per call, then 2 per competitor returned
Global Top Pages (Links API v2), Global Top Root Domains (Links API v2)
Not documented by Moz
Costs come from each method's page in the Moz API docs and may change; check the linked page for the current cost.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Moz API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
All templates except the two legacy ones send a JSON-RPC request to https://api.moz.com/jsonrpc. Settings described as JSON arrays are sent to Moz as-is, so they must be valid JSON; Moz rejects malformed requests before any quota is used.
This endpoint template returns the rows used and allotted in the current billing period for one Moz API quota, and whether overages are enabled. Use it to check your remaining quota before running other templates.
Quota: Free. Uses no quota.
Select the Quota: api.limits.data.rows (default; the main Moz API quota), api.limits.beta.rows (beta methods), or api.limits.mozscape.rows (used by List Site Competitors and the Links API).
This endpoint template returns the ID of the current Moz link index. The ID changes when Moz updates the index, so you can use it to decide when to refresh link data.
This endpoint template returns the top ranking competitors of a site, ordered by rivalry. Moz runs this method asynchronously: Nexla starts the request, then checks for the result every 10 seconds, up to 11 times.
Quota: Uses the Links API (mozscape) quota rather than data rows: 50 units are reserved for each call, then 2 units for each competitor returned. Checking for the result is free.
Enter the Site: a domain or URL, for example moz.com or https://moz.com/blog (default moz.com).
Select the Scope: domain, subdomain, or subfolder. The default is domain.
Select the Locale: en-US (default), en-GB, en-CA, or en-AU.
This endpoint template returns volume, difficulty, click-through rate, priority, and intent for up to 50 keywords, one record per keyword.
Quota: 1 row for each metric that has a value, up to 5 rows per keyword.
Enter Keywords (JSON) as a JSON array of up to 50 queries, each with keyword, locale, device, and engine, for example [{"keyword": "seo software", "locale": "en-US", "device": "desktop", "engine": "google"}].
This endpoint template returns one page of related keyword suggestions for a keyword (Google, desktop). Moz runs this method asynchronously: Nexla starts the request, then checks for the result every 10 seconds, up to 11 times.
Quota: 1 row for each suggestion returned. Checking for the result is free.
Enter the Keyword (1 to 255 characters).
Enter the Locale, for example en-US (default).
Select the Strategy: default (default), related_synonyms, or related_topics.
Enter the Page Number (starting at 0) and Max Results (1 to 50, default 25).
These two templates call the older Links API v2 at https://lsapi.seomoz.com/v2/ with the same API token. Prefer the free List Global Top Pages and List Global Top Domains templates for new flows.
Global Top Pages (Links API v2)
This endpoint template returns the top 500 pages in the Moz index by Page Authority, with link metrics, from the legacy Links API v2 (https://lsapi.seomoz.com/v2/global_top_pages). Nexla pages through all 500 results, 50 per call.
Quota: Not documented by Moz. List Global Top Pages returns the same data and is documented as free.
This endpoint template returns the top 500 root domains in the Moz index by Domain Authority, with link metrics, from the legacy Links API v2 (https://lsapi.seomoz.com/v2/global_top_root_domains). Nexla pages through all 500 results, 50 per call.
Quota: Not documented by Moz. List Global Top Domains returns the same data and is documented as free.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving. Testing a template calls Moz, so it uses quota unless the template is free.
Moz API data sources can also be manually configured to ingest data from any valid Moz API method not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Every Moz API method is called with POST at https://api.moz.com/jsonrpc, with a JSON body that names the method, for example {"jsonrpc": "2.0", "id": "my-request-id-0000000001", "method": "data.site.metrics.fetch", "params": {"data": {"site_query": {"query": "moz.com", "scope": "domain"}}}}. The id must be at least 24 characters of letters, numbers, and hyphens. Results are under $.result. The x-moz-token header is added automatically from your credential.
Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.