Skip to main content
POST
Reference example
The same per-period metrics as post_dataforseo_content_phrase_trends_live, but for an entire product category instead of one keyword. Takes category_code from get_dataforseo_content_categories, with date_from, date_to and date_group setting range and granularity, and returns a date plus total_count, rank, top_domains (each domain and count), sentiment_connotations (anger, happiness, love, sadness, share, fun), connotation_types (positive, negative, neutral), text_categories, page_categories, page_types, countries and languages per period. Every response wraps its payload in DataForSEO’s envelope - tasks[0].result holds the data. Use it to see how a market moves rather than a single phrase; swap to the phrase endpoint when you already know the exact wording you care about.

Example

First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. The commands per client, and what each call costs, are on aisa.one/mcp.
Set this endpoint up in your agent →

Cost and request rules

Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.0276
  • Cost contract: response_usd
  • Published reference multiplier: 1.0
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
category_code
integer | null

target category code
required field
to obtain a full list of available categories, refer to the Categories endpoint

page_type
string[] | null

target page types
optional field
use this parameter to filter the dataset by page types
possible values:
"ecommerce", "news", "blogs", "message-boards", "organization"

search_mode
string | null

results grouping type
optional field
possible grouping types:
as_is - returns data on all citations for the target category_code
one_per_domain - returns data on one citation of the category_code per domain
default value: as_is

internal_list_limit
integer | null

maximum number of elements within internal arrays
optional field
you can use this field to limit the number of elements within the following arrays:
top_domains
text_categories
page_categories
countries
languages
default value: 1
maximum value: 20

date_from
string

starting date of the time range
required field
minimum value: 2022-10-31
date format: "yyyy-mm-dd"
example:
"2019-01-15"

date_to
string | null

ending date of the time range
optional field
if you don't specify this field, today's date will be used by default
date format: "yyyy-mm-dd"
example:
"2019-01-15"

date_group
string | null

time range which will be used to group the results
optional field
default value: month
possible values: day, week, month

initial_dataset_filters
(object | null)[] | null

initial dataset filtering parameters
optional field
initial filtering parameters that apply to fields in the Search endpoint;
you can add several filters at once (8 filters maximum)
you should set a logical operator and, or between the conditions
the following operators are supported:
regex, not_regex, <, <=, >, >=, =, <>, in, not_in, like,not_like, has, has_not, match, not_match
you can use the % operator with like and not_like to match any string of zero or more characters
example:
["domain","<>", "logitech.com"]

[["domain","<>","logitech.com"],"and",["content_info.connotation_types.negative",">",1000]]

[["domain","<&gt","logitech.com"]],
"and",
[["content_info.connotation_types.negative",">",1000],
"or",

["content_info.text_category","has",10994]]]
for more information about filters, please refer to Content Analysis API - Filters
learn more about the initial dataset filters in this help center article.

rank_scale
string | null

defines the scale used for calculating and displaying the rank values
optional field

you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale

possible values:
one_hundred — rank values are displayed on a 0–100 scale
one_thousand — rank values are displayed on a 0–1000 scale

default value: one_thousand

learn more about how this parameter works in this Help Center article

tag
string | null

user-defined task identifier
optional field
the character limit is 255
you can use this parameter to identify the task and match it with the result
you will find the specified tag value in the data object of the response

Example:

Response

object | null

Successful operation

version
string | null

the current version of the API

status_code
integer | null

general status code you can find the full list of the response codes here

status_message
string | null

general informational message you can find the full list of general informational messages here

time
string | null

total execution time, seconds

cost
number<double> | null

total tasks cost, USD

tasks_count
integer<int64> | null

the number of tasks in the tasks array

tasks_error
integer<int64> | null

the number of tasks in the tasks array returned with an error

tasks
(object | null)[] | null

array of tasks