Traffic estimates over time
domain_traffic_history is a $0.20 GET request on the Wuthering AI API. Track estimated organic traffic for several domains across months. It answers complete JSON, and a call that fails is not charged.
Endpoint
GET /v1/domain_traffic_history
Price per successful call
$0.20
Failed calls
Not charged
curl 'https://wutheringai.com/v1/domain_traffic_history?targets=…&token=YOUR_TOKEN'
What does domain_traffic_history return, and when should you call it?
Return month-by-month estimated organic traffic for a set of domains over a date range.
Costs roughly ten times a standard call. This is how you see a competitor's growth curve, and how you catch a rival whose traffic collapsed six months ago while their marketing kept claiming otherwise.
Returns: per-target, per-month organic metrics including etv and keyword count.
Takes up to 50 domains and covers the last 24 months by default. Both bounds are narrower than the snapshot tool's because this endpoint bills by the domain AND by the month, so one open-ended call can cost more than the whole study around it. A larger set is several calls; a longer span is a second window.
Use when trajectory matters more than the current number. Don't use for a snapshot, where wuthering_domain_traffic takes a thousand domains for the same price.
What parameters does domain_traffic_history take?
domain_traffic_history accepts 5 parameters, of which 1 is required. Array values are comma-separated on the query string.
| Parameter | Type | Required | Description |
|---|---|---|---|
| targets | array | yes | Domains to track, up to 50. Every domain is billed, so send the competitive set you will actually read. |
| date_from | string | no | Earliest month to report, as YYYY-MM-DD. Defaults to 24 months before date_to, which is also the furthest back one call reaches. |
| date_to | string | no | Latest month to report, as YYYY-MM-DD. Defaults to the most recent data available. |
| location_code | number | no | Numeric location code to scope results to. Defaults to 2840 (United States). Search volume and competition vary sharply by country, so set this when the question is about a specific market.Defaults to 2840 |
| language_code | string | no | ISO language code for results, for example 'en' or 'de'. Defaults to 'en'.Defaults to en |
Which skills call domain_traffic_history?
3 of the research skills name domain_traffic_history in their method. Each is free to read and says where in the sequence the call belongs.
- Where is the unoccupied position in this category?Map the category around one domain as an idea maze — the forks it has already run, who took each branch, which walls are still walls and which have moved — then return the one open position with the offer that takes it: buyer, bundle, price metric and message, decided together.
- Is this company actually growing?Read one company's trajectory from public evidence: branded demand year over year, the acquisition engine underneath it, whether that demand was earned or bought, and what payroll says ships next — then name the questions only a data room can close.
- What would prove us wrong?Turn a belief the plan depends on into an explanation that cannot be bent to fit any result, name the rival explanations that would produce the same evidence, and pay only for the observations that would come out differently under each.
Reference for domain_traffic_history · last updated · published by Wuthering AI