POST /v3/content_analysis/search/live – DataForSEO API documentation

ContentAnalysis

Changed on Sep 9, 2026

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

post/v3/content_analysis/search/live

Request

Base URL: https://api.dataforseo.com
URL: https://api.dataforseo.com/v3/content_analysis/search/live
Auth: HTTP basic

Request body

keywordstring

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 <code>keyword</code> and <code>keywords</code> fields in DataForSEO APIs in this <a href="https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis" rel="noopener noreferrer" target="_blank">Help Center article</a>

keyword_fieldsobject nullable

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: <code>title</code>, <code>main_title</code>, <code>previous_title</code>, <code>snippet</code> 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" }"

page_typestring[] nullable

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

search_modestring nullable

results grouping type optional field possible grouping types: <code>as_is</code> - returns all citations for the target <code>keyword</code> <code>one_per_domain</code> - returns one citation of the <code>keyword</code> per domain default value: <code>as_is</code>

limitinteger nullable

the maximum number of returned citations optional field default value: <code>100</code> maximum value: <code>1000</code>

filtersobject[] nullable

array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator <code>and</code>, <code>or</code> between the conditions the following operators are supported: <code>regex</code>, <code>not_regex</code>, <code><</code>, <code><=</code>, <code>></code>, <code>>=</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>,<code>not_like</code>, <code>match</code>, <code>not_match</code> you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters example: <code>["country","=", "US"]</code><code>[["domain_rank",">",800],"and",["content_info.connotation_types.negative",">",0.9]]</code><code>[["domain_rank",">",800], "and", [["page_types","has","ecommerce"], "or",["content_info.text_category","has",10994]]]</code> for more information about filters, please refer to <a href="/v3/content_analysis/filters" target="_blank" rel="noopener noreferrer">Content Analysis API - Filters</a>

order_bystring[] nullable

results sorting rules optional field you can use the same values as in the <code>filters</code> array to sort the results possible sorting types: <code>asc</code> - results will be sorted in the ascending order <code>desc</code> - results will be sorted in the descending order you should use a comma to set up a sorting type example: <code>["content_info.sentiment_connotations.anger,desc"]</code> default rule: <code>["content_info.sentiment_connotations.anger,desc"]</code> note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: <code>["content_info.sentiment_connotations.anger,desc","keyword_data.keyword_info.cpc,desc"]</code>

offsetinteger nullable

offset in the results array of returned citations optional field default value: <code>0</code> if you specify the <code>10</code> 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 <code>offset_token</code> instead.

offset_tokenstring nullable

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 <code>offset_token</code> value from the response array, you will get the subsequent results of the initial task; <code>offset_token</code> values are unique for each subsequent task Note: if the <code>offset_token</code> is specified in the request, all other parameters except <code>limit</code> will not be taken into account when processing a task learn more about this parameter on our <a href="https://dataforseo.com/help-center/what-is-the-difference-between-the-offset-and-offset_token-parameters#offset_token" target="_blank">Help Center</a>

rank_scalestring nullable

defines the scale used for calculating and displaying the <code>domain_rank</code>, and <code>url_rank</code> values optional fieldyou can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scalepossible values: <code>one_hundred</code> — rank values are displayed on a 0–100 scale <code>one_thousand</code> — rank values are displayed on a 0–1000 scaledefault value: <code>one_thousand</code>learn more about how this parameter works in <a href="https://dataforseo.com/help-center/using-the-rank_scale-parameter-in-content-analysis-api">this Help Center article</a>

tagstring nullable

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 <code>tag</code> value in the <code>data</code> object of the response

Example request

[
  {
    "keyword_fields": {
      "snippet": "logitech"
    },
    "keyword": "logitech",
    "page_type": [
      "ecommerce",
      "news",
      "blogs",
      "message-boards",
      "organization"
    ],
    "search_mode": "as_is",
    "filters": [
      "main_domain",
      "=",
      "reviewfinder.ca"
    ],
    "order_by": [
      "content_info.sentiment_connotations.anger,desc"
    ],
    "limit": 10
  }
]

Response

Successful operation

versionstring nullable

the current version of the API

status_codeinteger nullable

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

status_messagestring nullable

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

timestring nullable

total execution time, seconds

costnumber double nullable

total tasks cost, USD

tasks_countinteger nullable

the number of tasks in the tasks array

tasks_errorinteger nullable

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

Changes

Sep 9, 20265948818f63bd Revision changes
- breaking
  added to the ///////////////////////////// response property oneOf list for the response status
- breaking
  added to the ///////////////////////// response property oneOf list for the response status
- info
  removed from the ///////////////////////////// response property oneOf list for the response status
- info
  removed from the ///////////////////////// response property oneOf list for the response status
Dec 14, 2025be20fca9d9cc Revision changes
- info
  api operation id ContentAnalysisSearchLive removed and replaced with SearchLive

Operation history (6 revisions)