DataForSEO: Content Analysis Category Trends Live

This endpoint will provide you with data on all citations in the target category for the indicated date range.

Tool ID: dataforseo_content_analysis_category_trends_live

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'dataforseo_content_analysis_category_trends_live',
  {
    "category_code": 123,
    "date_from": "2026-01-15T12:00:00Z"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute dataforseo_content_analysis_category_trends_live --input '{
  "category_code": 123,
  "date_from": "2026-01-15T12:00:00Z"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "version": "example",
  "status_code": 123,
  "status_message": "example",
  "time": "example",
  "tasks_count": 123,
  "tasks_error": 123,
  "tasks": [
    {}
  ]
}

Use deepline tools get dataforseo_content_analysis_category_trends_live --json for the latest machine-readable contract.

Input reference

This endpoint will provide you with data on all citations in the target category for the indicated date range.

Name	Type	Required	Default	Details
`payload.category_code`	`integer`	Yes	—	target category code required field to obtain a full list of available categories, refer to the Categories endpoint
`payload.page_type`	`array`	No	—	target page types optional field use this parameter to filter the dataset by page types possible values: “ecommerce” , “news” , “blogs” , “message-boards” , “organization”
`payload.search_mode`	`string`	No	—	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
`payload.internal_list_limit`	`integer`	No	—	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
`payload.date_from`	`string`	Yes	—	starting date of the time range required field minimum value: 2022-10-31 date format: “yyyy-mm-dd” example: “2019-01-15”
`payload.date_to`	`string`	No	—	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”
`payload.date_group`	`string`	No	—	time range which will be used to group the results optional field default value: month possible values: day , week , month
`payload.initial_dataset_filters`	`array`	No	—	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 See the live schema for the complete constraint.
`payload.rank_scale`	`string`	No	—	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
`payload.tag`	`string`	No	—	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

Output reference

Top-level response envelope for dataforseo_content_analysis_category_trends_live.

Name	Type	Required	Default	Details
`result.version`	`string`	Yes	—	the current version of the API
`result.status_code`	`integer`	Yes	—	general status code you can find the full list of the response codes here Note: we strongly recommend designing a necessary system for handling related exceptional or error conditions
`result.status_message`	`string`	Yes	—	general informational message you can find the full list of general informational messages here
`result.time`	`string`	Yes	—	execution time, seconds
`result.tasks_count`	`integer`	Yes	—	the number of tasks in the tasks array
`result.tasks_error`	`integer`	Yes	—	the number of tasks in the tasks array returned with an error
`result.tasks`	`array`	Yes	—	array of tasks

Deepline cost

Pricing model: provider_usage (provider usage).
Estimated Deepline credits: 0.01 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

DataForSEO: Content Analysis Category Trends Live

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation