Site Traffic API: Website Traffic Estimates for Millions of Domains

What you can do with website traffic data

Receive the estimated number of monthly visits for 5 million domains. We have seen the following use cases:

Lead scoring. Estimated traffic is a proxy for the importance of a company. Compare it to traffic of other operators in the same industry to see its relative importance.
Filtering publishers, affiliates and media outlets. Get an indicator of traffic before you pitch or pay for a placement.
Enriching domain lists in your own product or CRM.
PR and media measurement. Estimate the readership of every publication in a coverage report. This is what we built it for.
Replacing Alexa data in existing tools.

What you get with the Site Traffic API

One clear number. Estimated monthly visitors per domain. A domain metric anyone understands.
5 million domains. Our database covers millions of sites and their traffic.
Simple integration. A JSON response and one access token. You can test it with curl.
Batch requests. Send up to 250 domains in a single request to the batch endpoint and get a result for each one.
No surprises. Every response tells you how many credits you have left.
Tested in production. The same data sits behind the readership numbers in ReachReport coverage reports.

How the Site Traffic API works

Call the traffic endpoint with your API key and a domain:

curl "https://api.reachreport.io/api/traffic?access_token=API_KEY&url=google.com"

You get this back:

{
  "url": "google.com",
  "result": {
    "monthly_visitors": 15000000000
  },
  "credits": 99999
}

Read the Site Traffic API documentation

How we estimate website and domain traffic

We combine DNS requests from different data sets, public information and domain-specific signals to estimate how many visits a domain gets each month. Because the estimates start from DNS data, they include automated traffic. Read them as monthly visits, not unique visitors.

These are estimates, not first-party data. Only the site owner has exact numbers.

Why we built our own traffic API after Alexa

We are not the SaaS you'd expect to have traffic estimates, so what's the story? Our customers are PR agencies and communication professionals. They rely on ReachReport to estimate readership.

Alexa used to provide us with traffic estimates, but Amazon decided to sunset the service, and Alexa Rank went with it. So we developed our own, and now have a database with millions of sites and their traffic. We use it every day in our own product. Now you can use it too.

API for public relations and site traffic

Alternative to Similarweb and Semrush

Similarweb and Semrush offer full traffic analytics: traffic sources, countries, history and more. If you need all of that, they are the right tools. If you need a simple estimate per domain at an attractive rate, evaluate our API.

Site traffic API pricing

Each plan includes 20x the number of clips in API calls. The Startup plan, for example, covers up to 2,000 calls a month.

See plans and pricing

Works with Claude

ReachReport also has an MCP connector, so you can work with the data directly in Claude.

Read how the MCP connector works

Get your API key

Tell us about your use case in this short form and we'll send you an API key for testing.

Request API key

Website traffic API FAQs

How accurate are the website traffic estimates?

They are estimates, not measurements. The best way to evaluate the quality is asking for a test key and checking results against sites you know.

Which API should I use to get website traffic for a domain?

It depends on what you need. Use ours if you only need monthly estimated domain visits. For traffic sources, countries or history, look at Similarweb or Semrush.

Can I check the traffic of any website?

We cover 5 million domains. If a domain isn't in our database, the API returns a "not found" response.

Can I check many domains at once?

Yes. The batch endpoint takes up to 250 domains per request and returns a result for each one, or an error code if a domain isn't found or isn't valid.

Does the API include historical traffic data?

No. We only publish current estimates: one figure per domain, estimated monthly visitors.