DataForSEO: Content Analysis Search Live

This endpoint will provide you with detailed citation data available for the target keyword.

Tool ID: dataforseo_content_analysis_search_live

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'dataforseo_content_analysis_search_live',
  {
    "keyword": "software companies hiring engineers"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute dataforseo_content_analysis_search_live --input '{
  "keyword": "software companies hiring engineers"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

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

Use deepline describe dataforseo_content_analysis_search_live --json for the latest machine-readable contract.

Input reference

This endpoint will provide you with detailed citation data available for the target keyword.

Name	Type	Required	Default	Details
`payload.keyword`	`string`	Yes	—	target keyword required field UTF-8 encoding the keywords will be converted to a lowercase format. Note : to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes. example: “keyword”: ""tesla palo alto"" learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article
`payload.keyword_fields`	`object`	No	—	target keyword fields and target keywords optional field use this parameter to filter the dataset by keywords that certain fields should contain. fields you can specify: title , main_title , previous_title , snippet you can indicate several fields. Note : to match an exact phrase instead of a stand-alone keyword, use double quotes and backslashes. example: “keyword_fields”: { “snippet”: ""logitech mouse"", “main_title”: “sale” }
`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 all citations for the target keyword one_per_domain - returns one citation of the keyword per domain default value: as_is
`payload.limit`	`integer`	No	—	the maximum number of returned citations optional field default value: 100 maximum value: 1000
`payload.filters`	`array`	No	—	array of results filtering parameters optional field 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 , match , not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [“country”,”=”, “US”] See the live schema for the complete constraint.
`payload.order_by`	`array`	No	—	results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc - results will be sorted in the ascending order desc - results will be sorted in the descending order you should use a comma to set up a sorting type example: [“content_info.sentiment_connotations.anger,desc”] default rule: [“content_info.sentiment_connotations.anger,desc”] note that you can set no more than three sorting rules in a single request you should See the live schema for the complete constraint.
`payload.offset`	`integer`	No	—	offset in the results array of returned citations optional field default value: 0 if you specify the 10 value, the first ten citations in the results array will be omitted and the data will be provided for the successive citations Note: we recommend using this parameter only when retrieving up to 10,000 results for retrieving over 10,000 results, use the offset_token instead.
`payload.offset_token`	`string`	No	—	offset token for subsequent requests optional field provided in the identical field of the response to each request. Use this parameter to avoid timeouts while trying to obtain over 10,000 results in a single request. by specifying the unique offset_token value from the response array, you will get the subsequent results of the initial task. offset_token values are unique for each subsequent task Note: if the offset_token is specified in the request, all other parameters except limit will not be See the live schema for the complete constraint.
`payload.rank_scale`	`string`	No	—	defines the scale used for calculating and displaying the domain_rank , and url_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_search_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.

​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