Skip to content
SEO API

Website Traffic

Monthly organic traffic history for any domain.

Start free Try it
POST /api/v1/website/traffic$0.01 / requestAuth: X-API-Key header
seonio / rest apiFrom the API docs
RequestPOST /api/v1/website/traffic
curl -X POST https://seonio.com/api/v1/website/traffic \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $SEONIO_API_KEY" \
  -d '{"domain_name": "moz.com"}'
Response200 OK
{
  "domain_name": "moz.com",
  "organic_monthly": [
    {
      "month": "2022-01",
      "value": 4535536
    },
    {
      "month": "2022-02",
      "value": 3561567
    },
    {
      "month": "2022-03",
      "value": 3742624
    },
    {
      "month": "2026-04",
      "value": 2613035
    },
    {
      "month": "2026-05",
      "value": 2428505
    }
  ]
}
Contract

What to send and what comes back

Get a clean monthly organic-traffic series for a domain — perfect for trend charts, competitor tracking and growth/decline detection.

Request body

Request body
FieldTypeRequiredDescription
domain_name string required Bare domain to analyse, e.g. "moz.com".

Response

Response fields
FieldTypeDescription
domain_name string The domain that was analysed.
organic_monthly[] object[] Monthly organic traffic points, oldest to newest, each as { month: YYYY-MM, value }.
Code

Copy, paste, add your key

The same request in cURL, Python and Node.js.

cURL
curl -X POST https://seonio.com/api/v1/website/traffic \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{"domain_name": "moz.com"}'
Python
import requests

resp = requests.post(
    "https://seonio.com/api/v1/website/traffic",
    headers={"X-API-Key": "YOUR_API_KEY"},
    json={"domain_name": "moz.com"},
)
print(resp.json())
Node.js
const resp = await fetch("https://seonio.com/api/v1/website/traffic", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-Key": "YOUR_API_KEY",
  },
  body: JSON.stringify({"domain_name": "moz.com"}),
});
console.log(await resp.json());
Playground

Run a real request

Send this request from your browser with your API key, or leave the key empty to see the sample response.

A successful run costs $0.01 / request. With no key, you see the sample response and nothing is charged.

POST /api/v1/website/trafficSample response
{
  "domain_name": "moz.com",
  "organic_monthly": [
    {
      "month": "2022-01",
      "value": 4535536
    },
    {
      "month": "2022-02",
      "value": 3561567
    },
    {
      "month": "2022-03",
      "value": 3742624
    },
    {
      "month": "2026-04",
      "value": 2613035
    },
    {
      "month": "2026-05",
      "value": 2428505
    }
  ]
}
Use cases

What developers build with it

  • Traffic trend charts on a domain overview page.
  • Competitor monitoring and alerting on drops.
  • Lead qualification by estimated organic reach.
Status codes

The same contract on every endpoint

Error responses are JSON with a "detail" field. It is a message string unless the row above says otherwise.

Status codes
CodeWhen
200Success. The lookup completed and was charged, even if the response is empty. /keywords/global charges only the keywords it looked up.
401Missing or unknown API key.
402Not enough balance. "detail" is an object with "error", "message", "balance_required" and "balance_available". Requests still running hold their price until they finish, so a retry can succeed once they do.
403The account is not verified yet, or it is locked.
422Invalid request (wrong shape or types, a keyword over 200 characters, a URL the page checker cannot audit, a domain that does not exist, or a bare public suffix such as co.uk that groups many websites) — never charged. "detail" is usually a list of validation errors; an answer that retrying cannot change (such as a domain without a DNS record) is a message string with an X-Outcome header naming it: missing, unsupported, too_large or refused_input.
429Rate limit exceeded, never charged. Requests per second per account by plan: 5 on a free account, 10 on Starter, 15 on Pro and 20 on Business; retry after the Retry-After header. Also the page checker's provider limit.
503A data provider failed or timed out (X-Outcome: temporary). Nothing was charged; retry after the seconds in the Retry-After header.
FAQ

Questions, answered

Simple answers for developers using the API.

Every endpoint has a published USD price or formula. Requests draw from the same testing, included and Extra Usage balance as website and MCP actions: testing first, then included usage, then Extra Usage expiring soonest.

API actions require a verified account with a free $1 balance or an active subscription balance. Create and manage API keys from your account, then send the key in the X-API-Key header.

Yes. Your account shows API usage and remaining balance, so you can track costs while building and running automated workflows.

REST API and MCP requests per second depend on your plan: 5 on a free account, 10 on Starter, 15 on Pro and 20 on Business. Website data requests from the same account count toward the same second. Requests above the limit return HTTP 429 with a Retry-After header and are not charged; wait a second and retry.

Free $1 to test · No card required

Turn search insights into measurable growth

Start your SEO research in seconds.

Get started for free See pricing
SEO researchREST APIMCP