Moz

Log in to moz.com and navigate to moz.com/products/pro/api (or find the API section under your account dashboard). You will see two credentials: - Access ID: a string that looks like mozscape-xxxxxxxxxxxxxxxx - Secret Key: a longer alphanumeric string Copy both. Now you need to compute the Basic Auth string that goes into Bubble's API Connector. HTTP Basic Auth encodes the credentials as base64(AccessID:SecretKey). Here is how to do this in 10 seconds: 1. Open any webpage in your browser (even a blank tab). 2. Press F12 to open Developer Tools. 3. Click the Console tab. 4. Type the following, replacing with your actual credentials: btoa('YOUR_ACCESS_ID:YOUR_SECRET_KEY') 5. Press Enter. The console returns a base64-encoded string like: bW96c2NhcGUteHh4Onl5eXl5 6. The complete Authorization header value you will use is: Basic bW96c2NhcGUteHh4Onl5eXl5 Store this base64 string (not the raw credentials) — it is what you will paste into Bubble. This is a one-time computation. If you regenerate your Moz credentials, you will need to recompute the base64 string. Important: the colon between Access ID and Secret Key in the btoa() call is required. Omitting it or reversing the order will produce a different base64 string that will not authenticate with Moz's API.

1// Run this in your browser console (F12 → Console tab)
2// Replace with your actual Moz credentials
3btoa('mozscape-xxxxxxxxxxxxxxxx:your-secret-key-here')
4
5// Output example: 'bW96c2NhcGUteHh4eHh4eHh4eHh4OnNlY3JldGtleQ=='
6
7// Full Authorization header value:
8// Basic bW96c2NhcGUteHh4eHh4eHh4eHh4OnNlY3JldGtleQ==
9
10// Format: 'Basic ' + btoa('ACCESS_ID:SECRET_KEY')
11// The word 'Basic' followed by a space is REQUIRED

In your Bubble app editor, click the Plugins tab in the left sidebar. Click 'Add plugins', search for 'API Connector' (the free official plugin by Bubble), and install it. After installation, click the API Connector in your plugins list to open it, then click 'Add another API'. Name this API 'Moz API'. Set the Base URL to: https://lsapi.seomoz.com/v2 Click 'Add a shared header'. In the Key field, enter: Authorization. In the Value field, paste your precomputed string in the format 'Basic [your-base64-string]' — for example: Basic bW96c2NhcGUteHh4eHh4eHh4eHh4OnNlY3JldGtleQ== Check the 'Private' checkbox next to this header. This is the critical step — the Private checkbox ensures Bubble stores this header on its servers and never sends it to the browser. Even though the credentials are already base64-encoded (not encrypted), marking them Private prevents exposure in browser network logs or page source. Also add a Content-Type shared header: Key = Content-Type, Value = application/json, Private = unchecked. The Moz API requires this for POST requests. Do not add any other credentials to individual calls — the shared Authorization header covers all calls made under this API entry.

1{
2  "api_name": "Moz API",
3  "base_url": "https://lsapi.seomoz.com/v2",
4  "shared_headers": [
5    {
6      "key": "Authorization",
7      "value": "Basic YOUR_BASE64_ENCODED_CREDENTIALS",
8      "private": true
9    },
10    {
11      "key": "Content-Type",
12      "value": "application/json",
13      "private": false
14    }
15  ]
16}

The primary Moz Links API endpoint for this integration is POST /url_metrics, which accepts a JSON body containing an array of up to 50 target URLs and returns DA, PA, Spam Score, and link count data for each. In the API Connector under your Moz API entry, click 'Add another call'. Name it 'batch_url_metrics'. Set the method to POST. In the URL path field, enter: /url_metrics (this appends to the base URL to form https://lsapi.seomoz.com/v2/url_metrics). In the Body section, set the content type to 'JSON' and enter the request body structure: {"targets": ["[domain]"]} The [domain] parameter should be set as a dynamic value. Add a parameter named 'targets' as a JSON array body parameter. Since this is a batch endpoint that takes multiple domains, you will pass the array programmatically from your Bubble Workflow — but for initialization purposes, use a test value like {"targets": ["moz.com", "example.com"]}. Set 'Use as' to Action — even though this call returns data, it is a POST request. Bubble treats it as an Action, and you can still read the result object in workflow steps. Click 'Initialize call'. If the Authorization header is correctly configured, Moz will return DA, PA, and metrics for the test domains. Bubble will auto-detect the response fields. Verify that the response shows a 'results' array with items containing: domain_authority, page_authority, spam_score, root_domains_to_root_domain, and external_equity_links fields.

1POST https://lsapi.seomoz.com/v2/url_metrics
2
3Headers:
4  Authorization: Basic <private>
5  Content-Type: application/json
6
7Body:
8{
9  "targets": [
10    "moz.com",
11    "example.com"
12  ]
13}
14
15Response shape:
16{
17  "results": [
18    {
19      "page": "moz.com",
20      "domain_authority": 91,
21      "page_authority": 71,
22      "spam_score": 2,
23      "root_domains_to_root_domain": 42318,
24      "external_equity_links": 1054321
25    }
26  ]
27}

Moz API credits are consumed per URL in a batch — 50 URLs in one POST request = 50 credits against your monthly plan limit. Moz updates DA scores on a monthly cycle, so there is no benefit to calling the API more often than that for the same domain. Store results in a Bubble Data Type and check the cache before making API calls. Go to the Data tab in your Bubble editor. Click 'New type' and name it 'Domain_Authority'. Add these fields by clicking 'Create a new field' for each: - domain: Text (the domain URL, e.g., 'competitor.com') - da: Number (domain_authority from API) - pa: Number (page_authority from API) - spam_score: Number - root_domains: Number (root_domains_to_root_domain) - equity_links: Number (external_equity_links) - fetched_date: Date (when this record was last updated from the Moz API) Go to Data tab → Privacy for the Domain_Authority Data Type. Set privacy rules so that 'Everyone else' cannot read or search these records — your DA data is business-sensitive information about your competitors. Enable access only for appropriate user roles in your app. The domain field should be treated as a unique identifier. Before creating a new Domain_Authority record, always search for an existing one with the same domain value and update it rather than creating a duplicate.

1Data Type: Domain_Authority
2Fields:
3  - domain: Text (the domain name, e.g., competitor.com)
4  - da: Number (Moz domain_authority score, 0-100)
5  - pa: Number (Moz page_authority score, 0-100)
6  - spam_score: Number (0-100; higher = more spammy)
7  - root_domains: Number (unique root domains linking in)
8  - equity_links: Number (total external equity links)
9  - fetched_date: Date (when last synced from Moz)
10
11Privacy rules:
12  Everyone else → Find in searches: No
13  Everyone else → Read: No
14  Admin role → All permissions: Yes

The batch lookup workflow takes a list of domain names, checks the cache for each, collects the ones that need refreshing, sends them to Moz in batches of 50, and stores the results. Here is the architecture: In your Bubble app, create a page with a Multi-line Input for domain names (one per line) and a 'Get DA Scores' button. Workflow: 'Get DA Scores' button is clicked Step 1: Split the Multi-line Input's value into a list by line break. In Bubble, use ':split by' operator with the newline character. Store this as a Custom State (type: list of text) named 'domain_list'. Step 2: For each domain in domain_list, check if a fresh Domain_Authority record exists (fetched_date > Current date/time minus 30 days). Collect only the domains that need a fresh score. Step 3: Call batch_url_metrics with the domains that need refreshing. Since the POST body requires a JSON array, and Bubble's API Connector expects the body as a text field, format the list as a JSON string: '["domain1.com","domain2.com"]'. Step 4: For each result in the API response's results array, create or update a Domain_Authority record: domain = result's page, da = result's domain_authority, pa = result's page_authority, spam_score = result's spam_score, fetched_date = Current date/time. Batch size limitation: the Moz API accepts a maximum of 50 URLs per POST request. For lists longer than 50 domains, implement a recursive Backend Workflow that processes 50 domains at a time. RapidDev's team has built this exact batching pattern for Bubble SEO tools — if you need help architecting the recursive loop for large domain lists, reach out at rapidevelopers.com/contact.

1Workflow: 'Get DA Scores' button clicked
2
3Step 1: Set Custom State 'domain_list' = MultilineInput's value :split by '\n' :filter where not empty
4
5Step 2: Identify stale domains:
6  For each domain in domain_list:
7    If Search Domain_Authority where domain=current item AND fetched_date > current date-30days, count = 0
8    → add to 'needs_refresh' custom state (list of text)
9
10Step 3 [Only when needs_refresh count > 0]:
11  Call API → Moz API - batch_url_metrics
12  Body: {"targets": [needs_refresh as JSON array]}
13  Result name: moz_results
14
15Step 4: For each item in moz_results's results:
16  If Domain_Authority exists where domain = item's page:
17    Make changes: da=item's domain_authority, pa=item's page_authority,
18                  spam_score=item's spam_score, fetched_date=current date
19  Else:
20    Create Domain_Authority: domain=item's page, da=item's domain_authority,
21    pa=item's page_authority, spam_score=item's spam_score,
22    root_domains=item's root_domains_to_root_domain,
23    equity_links=item's external_equity_links, fetched_date=current date
24
25Batch cap: 50 domains per POST request
26For lists > 50: use recursive Backend Workflow, batch items 1-50, then 51-100, etc.

With data stored in Domain_Authority, the Repeating Group display is straightforward and highly customizable. Select your Repeating Group on the canvas. Configure: - Type of content: Domain_Authority - Data source: Do a search for Domain_Authority items, sorted by da descending Add filtering controls: a Number Input for minimum DA threshold and a Checkbox for 'Only show Spam Score < 30'. Connect these to the data source with constraints. Inside the Repeating Group cell, add Text elements: - Domain: Current cell's Domain_Authority's domain - DA Score: Current cell's Domain_Authority's da (formatted as number) - PA Score: Current cell's Domain_Authority's pa - Spam Score: Current cell's Domain_Authority's spam_score - Last Updated: Current cell's Domain_Authority's fetched_date (formatted as 'MMM D, YYYY') For the DA Score text element, add Conditional styling: - Conditional 1: When Current cell's Domain_Authority's da > 69 → Background color: green (light) - Conditional 2: When Current cell's Domain_Authority's da > 39 AND ≤ 69 → Background color: yellow (light) - Conditional 3: When Current cell's Domain_Authority's da ≤ 39 → Background color: red (light) Add a 'Force Refresh' icon button for each row that triggers a single-domain batch_url_metrics call (with a one-domain targets array) and updates the specific Domain_Authority record. This gives users an escape valve when they know a domain's authority has changed recently without waiting for the 30-day cache expiry.

1Repeating Group configuration:
2  Type of content: Domain_Authority
3  Data source: Search Domain_Authority
4    Constraint: da ≥ MinimumDA Input's value (optional filter)
5    Sort: da, Descending
6
7Cell elements:
8  Text 'Domain': Current cell's Domain_Authority's domain
9  Text 'DA': Current cell's Domain_Authority's da
10    Conditional: da > 69 → background #d4edda (green)
11    Conditional: da 40-69 → background #fff3cd (yellow)
12    Conditional: da < 40 → background #f8d7da (red)
13  Text 'PA': Current cell's Domain_Authority's pa
14  Text 'Spam': Current cell's Domain_Authority's spam_score
15    Conditional: spam_score > 30 → text color red, add warning icon
16  Text 'Updated': Current cell's Domain_Authority's fetched_date
17    Format: MMM D, YYYY
18
19Force Refresh button workflow:
20  Step 1: Call batch_url_metrics
21    Body: {"targets": ["[Current cell's Domain_Authority's domain]"]}
22  Step 2: Make changes to Current cell's Domain_Authority
23    da: Result Step 1's results:first item's domain_authority
24    pa: Result Step 1's results:first item's page_authority
25    spam_score: Result Step 1's results:first item's spam_score
26    fetched_date: Current date/time