Semrush Gateway API

Returns one result row per requested target, in request order.

curl -X POST https://api.seo1.us/v1/bulk-analysis \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "targets": [
      {"target": "amazon.com",  "target_type": "root_domain"},
      {"target": "apple.com",   "target_type": "root_domain"},
      {"target": "shopify.com", "target_type": "root_domain"}
    ]
  }'

{
  "success": true,
  "count": 1,
  "results": [
    {
      "target": "apple.com",
      "target_type": "root_domain",
      "authority_score": 100,
      "total_backlinks": 6162246181,
      "referring_domains": 5761755,
      "follow": 4879470067,
      "nofollow": 1262596675,
      "text": 3206326108,
      "image": 2136212652,
      "ips": 1318698,
      "outbound_links": 16861408,
      "outbound_domains": 905859,
      "error": null
    }
  ],
  "request_id": "5846269872b6438284f292770c458d35"
}

The same bulk-analysis data, returned as a CSV file in one request.

curl -o bulk.csv \
  "https://api.seo1.us/v1/bulk-analysis/export?targets=amazon.com,apple.com,shopify.com" \
  -H "X-API-Key: smg_your_api_key"

Columns: target, target_type, authority_score, total_backlinks, referring_domains, follow, nofollow, text, image, ips, outbound_links, outbound_domains, error.

Returns target-level totals plus a backlinks[] array.

curl -X POST https://api.seo1.us/v1/backlinks \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"target": "example.com", "target_type": "root_domain", "limit": 100}'

Each row in backlinks[] includes source_url, anchor, is_nofollow, source_ascore, and domain_ascore, alongside top-level authority_score, total_backlinks, and referring_domains.

The full backlinks dataset as a CSV file, in one request.

curl -o backlinks.csv \
  "https://api.seo1.us/v1/backlinks/export?target=example.com&target_type=root_domain&export_type=backlinks" \
  -H "X-API-Key: smg_your_api_key"

Same body shape as /v1/backlinks; defaults to sorting by domain_ascore.

curl -X POST https://api.seo1.us/v1/referring-domains \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"target": "example.com", "target_type": "root_domain", "limit": 100}'

Each row includes domain, domain_ascore, backlinks_num, ip, country, first_seen, and last_seen.

The top N referring domains (default and max 1000), ordered by domain_ascore descending. CSV by default, or JSON with format=json.

The native upstream CSV export is disabled by every data source, so the gateway assembles this itself: it paginates the working POST /v1/referring-domains endpoint (100 rows per page, offsets 0…900) through the load-balancer, then dedupes, sorts, and truncates to max_rows. You get the highest-authority referring domains first.

curl -o referring_domains.csv \
  "https://api.seo1.us/v1/referring-domains/export?target=backlinko.com&target_type=root_domain" \
  -H "X-API-Key: smg_your_api_key"

CSV (default): text/csv attachment. Columns, in order: domain, domain_ascore, backlinks_num, ip, country, first_seen, last_seen.

JSON (format=json): { success, target, target_type, total_available, returned, referring_domains[], request_id }.

Response headers: X-Source: paginated, X-Provider: composite, X-Total-Available (e.g. 73370), X-Rows-Returned, and X-Partial: true only if an internal page hard-failed. Small sites stop early once a page returns fewer than 100 rows.

The gateway automatically routes this to a data source that supports it.

curl -X POST https://api.seo1.us/v1/indexed-pages \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"target": "example.com", "target_type": "root_domain", "limit": 100}'

The gateway automatically routes this to the data source that supports anchor data.

curl -X POST https://api.seo1.us/v1/anchors \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"target": "example.com", "target_type": "root_domain", "limit": 100}'

Returns top-level overview counts plus an outbound_domains[] array.

curl -X POST https://api.seo1.us/v1/outbound-domains \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"domain": "example.com", "limit": 100}'

Includes top-level authority_score, referring_domains, total_backlinks, and outbound_links.

The outbound domains a site links out to (default and max 1000), ordered by domain_ascore descending. CSV by default, or JSON with format=json.

The native upstream CSV export is disabled by every data source, so the gateway assembles this from the working POST /v1/outbound-domains endpoint. That POST caps at 100 rows/call and ignores pagination, but different sort orders return different 100-row slices — so for max_rows > 100 the gateway fans out across 8 sort orders concurrently and unions the distinct domains (verified: full set recovered), then dedupes, sorts by your sort_field/sort_type, and truncates to max_rows. Requests with max_rows ≤ 100 take a single-call fast path. Quota counts once.

curl -o outbound_domains.csv \
  "https://api.seo1.us/v1/outbound-domains/export?domain=hasselblad.com" \
  -H "X-API-Key: smg_your_api_key"

CSV (default): text/csv attachment. Columns, in order: domain, domain_ascore, links_num, category, first_seen, last_seen.

JSON (format=json): { success, domain, total_available, returned, outbound_domains[], request_id }.

Response headers: X-Source (multi-sort-union or single-call), X-Provider: composite, X-Total-Available, X-Rows-Returned, and X-Partial: true if a sort slice failed.

Returns a domains[] array with per-target backlink counts. Backed only by NoxTools — retry after ~60s if rate-limited.

curl -X POST https://api.seo1.us/v1/backlinks-gap \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"targets": ["backlinko.com", "ahrefs.com"], "gap_type": "all", "limit": 2}'

Each row in domains[] includes domain, domain_ascore, matches_num, backlinks_num (per-target counts in targets order), and traffic.

filters object

All optional: volume_min/volume_max, kd_min/kd_max, cpc_min/cpc_max, word_count_min/word_count_max, include_phrases[], exclude_phrases[], intent[], serp_features[].

curl -X POST https://api.seo1.us/v1/keyword-research \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "phrase": "running shoes",
    "database": "us",
    "match_type": "broad",
    "max_pages": 2,
    "filters": { "volume_min": 500, "kd_max": 40 }
  }'

The same keyword data, streamed back as text/csv. Takes the same body minus page/page_size; defaults to max_pages: 10.

curl -o keywords.csv -X POST https://api.seo1.us/v1/keyword-research/csv \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"phrase": "running shoes", "database": "us", "max_pages": 10}'

Response headers include X-Total-Available and X-Rows-Returned so you can tell how much data was available versus returned.

Returns a sorted countries[] array with per-database traffic and positions.

curl -X POST https://api.seo1.us/v1/top-countries \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"domain": "example.com"}'

Native-first with automatic composite fallback. The native upstream (NoxTools) is tried first; it is often Semrush rate-limited. When native is unavailable the gateway transparently computes the gap by diffing ranked-keywords (served by all 5 providers), so the endpoint stays reliable. The path used is reported via the X-Gap-Source header (native | composite) and the source field (composite only). Quota counts once per request regardless of internal calls.

curl -X POST https://api.seo1.us/v1/keyword-gap \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"targets": ["backlinko.com", "ahrefs.com"], "database": "us", "type": 2, "limit": 2}'

Native response (X-Gap-Source: native) — passed through verbatim. Each row in keywords[] includes keyword, volume, keyword_difficulty, cpc, competition, intents, plus positions and urls (per-target, in targets order).

Composite response (X-Gap-Source: composite) — the keywords any competitor ranks for that the target (first domain) does not. Adds top-level source, target, competitors and a note. Each row in keywords[] includes phrase, volume, keyword_difficulty, cpc, intents, plus competitor, competitor_position (best/lowest) and url. If the target's own ranked-keywords lookup fails, the response adds target_ranked_unavailable: true (diff is incomplete). If ranked-keywords fails for every domain, you get the standard 503.

Returns a keywords[] array plus total_volume.

curl -X POST https://api.seo1.us/v1/bulk-keyword-volume \
  -H "X-API-Key: smg_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["cnc machining", "metal fabrication"], "database": "us"}'

Each row in keywords[] includes phrase, volume, cpc, competition, keyword_difficulty, intents, serp_features, trends, and click_potential. Top-level: requested, returned, total_volume.

curl https://api.seo1.us/health

{
  "status": "ok",
  "providers": [
    {"name": "a", "enabled": true, "healthy": true,  "breaker": "closed", "in_flight": 0},
    {"name": "b", "enabled": true, "healthy": true,  "breaker": "closed", "in_flight": 2}
  ]
}

As long as status is ok and at least one source is healthy, the API serves requests — failover handles the rest.