Dataforseo Trends Merged Data Live
/keywords_data_dataforseo_trends_merged_data_liveThis endpoint will provide you with the keyword popularity data from DataForSEO Trends. In addition to keyword popularity rate over the given time range, you will get location-specific keyword popularity data, and a demographic breakdown of keyword popularity per each specified term along with comparative values.
- Finished calls, last 7 days
- 0
Cancellations excluded. Execution times cover successful calls.
Use it with your agent
Set up https://www.agentrouter.to/SKILL.md, then use DataForSEO’s /keywords_data_dataforseo_trends_merged_data_live endpoint through AgentRouter.
Inputs
keywordsRequired- keywords required field the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article
location_nameOptional- full name of search engine location optional field if you don't use this field, you will recieve global results if you use this field, you don't need to specify location_code you can receive the list of available locations of the search engine with their location_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_name belongs to; example: United Kingdom
location_codeOptional- search engine location code optional field if you don't use this field, you will recieve global results if you use this field, you don't need to specify location_name you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_code belongs to; example: 2840
typeOptional- type of element
date_fromOptional- starting date of the time range optional field if you don't specify this field, the current day and month of the preceding year will be used by default minimal value for the web type: 2004-01-01 minimal value for other types: 2008-01-01 date format: "yyyy-mm-dd" example: "2019-01-15"
date_toOptional- ending date of the time range optional field if you don't specify this field, the today's date will be used by default date format: "yyyy-mm-dd" example: "2019-01-15"
time_rangeOptional- preset time ranges optional field if you specify date_from or date_to parameters, this field will be ignored when setting a task possible values for all type parameters: past_4_hours , past_day , past_7_days , past_30_days , past_90_days , past_12_months , past_5_years
Example input
{
"keywords": [
"rugby",
"cricket"
],
"date_from": "2023-01-01",
"date_to": "2024-01-01",
"type": "web",
"location_name": "United States"
}Output
Native task result envelope; includes items, aggregates and pagination where supported.