dataforseo-client 2.1.2 → 2.1.3

package/dist/cjs/models/DataforseoLabsGoogleDomainIntersectionLiveRequestInfo.d.ts

@@ -1,66 +1,66 @@
 export interface IDataforseoLabsGoogleDomainIntersectionLiveRequestInfo {
-    /** domain required field the domain name of the first target website the domain should be specified without https:// and www. */
+    /** *domain*             **required field**             the domain name of the first target website             the domain should be specified without `https://` and `www.` */
     target_1?: string | undefined;
-    /** domain required field the domain name of the second target website the domain should be specified without https:// and www. */
+    /** *domain*             **required field**             the domain name of the second target website             the domain should be specified without `https://` and `www.` */
     target_2?: string | undefined;
-    /** full name of the location required field if you don’t specify location_code Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: United Kingdom */
+    /** *full name of the location*             **required field if you don't specify** `location_code`             **Note:** it is required to specify either `location_name` or `location_code`             you can receive the list of available locations with their `location_name` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `United Kingdom` */
     location_name?: string | undefined;
-    /** location code required field if you don’t specify location_name Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: 2840 */
+    /** *location code*             **required field if you don't specify** `location_name`             **Note:** it is required to specify either `location_name` or `location_code`             you can receive the list of available locations with their `location_code` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `2840` */
     location_code?: number | undefined;
-    /** full name of the language required field if you don’t specify language_code Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: English */
+    /** *full name of the language*             **required field if you don't specify** `language_code`             **Note:** it is required to specify either `language_name` or `language_code`             you can receive the list of available languages with their `language_name` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `English` */
     language_name?: string | undefined;
-    /** language code required field if you don’t specify language_name Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: en */
+    /** *language code*             **required field if you don't specify** `language_name`             **Note:** it is required to specify either `language_name` or `language_code`             you can receive the list of available languages with their `language_code` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `en` */
     language_code?: string | undefined;
-    /** domain intersections in SERP optional field if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million if you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t; thus, the corresponding SERP elements and other data will be provided for the domain specified as target1only default value: true */
+    /** *domain intersections in SERP*             optional field             if you set intersections to `true`, you will get the keywords for which both target domains specified as `target1` and `target2` have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array             **Note:** this endpoint will not provide results if the number of intersecting keywords exceeds 10 million             if you specify `intersections: false`, you will get the keywords for which the domain specified as `target1` has results in SERP, and the domain specified as `target2` doesn't;             thus, the corresponding SERP elements and other data will be provided for the domain specified as `target1`only             default value: `true` */
     intersections?: boolean | undefined;
-    /** search results type indicates type of search results included in the response optional field possible values: ['organic', 'paid', 'featured_snippet', 'local_pack'] default value: ['organic', 'paid'] */
+    /** *search results type*             indicates type of search results included in the response             optional field             possible values:             `['organic', 'paid', 'featured_snippet', 'local_pack']`             default value:             `['organic', 'paid']` */
     item_types?: string[] | undefined;
-    /** include data from SERP for each keyword optional field if set to true, we will return a serp_info array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response default value: false */
+    /** *include data from SERP for each keyword*             optional field             if set to `true`, we will return a `serp_info` array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response             default value: `false` */
     include_serp_info?: boolean | undefined;
-    /** include or exclude data from clickstream-based metrics in the result optional field if the parameter is set to true, you will receive clickstream_keyword_info, clickstream_etv, keyword_info_normalized_with_clickstream, and keyword_info_normalized_with_bing fields in the response default value: false with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this help center article */
+    /** *include or exclude data from clickstream-based metrics in the result*             optional field             if the parameter is set to `true`, you will receive `clickstream_keyword_info`, `clickstream_etv`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response             default value: `false`             with this parameter enabled, you will be charged double the price for the request             learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
     include_clickstream_data?: boolean | undefined;
-    /** the maximum number of returned keywords optional field default value: 100 maximum value: 1000 */
+    /** *the maximum number of returned keywords*             optional field             default value: `100`             maximum value: `1000` */
     limit?: number | undefined;
-    /** offset in the items array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
+    /** *offset in the `items` array of returned keywords*             optional field             default value: `0`             if you specify the `10` value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
     offset?: number | undefined;
-    /** 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, match, not_match, ilike, not_ilike, like, not_like you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters example: ['keyword_data.keyword_info.search_volume','in',[100,1000]] [['first_domain_serp_element.etv','>',0],'and',['first_domain_serp_element.description','like','%goat%']] [['keyword_data.keyword_info.search_volume','>',100], 'and', [['first_domain_serp_element.description','like','%goat%'], 'or', ['second_domain_serp_element.type','=','organic']]] for more information about filters, please refer to Dataforseo Labs – Filters or this help center guide */
+    /** *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`, `match`, `not_match`, `ilike`, `not_ilike`, `like`, `not_like`             you can use the `%` operator with `like` and `not_like`, as well as `ilike` and `not_ilike` to match any string of zero or more characters             example:             `['keyword_data.keyword_info.search_volume','in',[100,1000]]`             `[['first_domain_serp_element.etv','>',0],'and',['first_domain_serp_element.description','like','%goat%']]`             `[['keyword_data.keyword_info.search_volume','>',100],                'and',                [['first_domain_serp_element.description','like','%goat%'],                'or',                ['second_domain_serp_element.type','=','organic']]]`             for more information about filters, please refer to [Dataforseo Labs - Filters](/v3/dataforseo_labs/filters) or this [help center guide](https://dataforseo.com/help-center/how-to-use-filters-in-dataforseo-labs-api) */
     filters?: any[] | undefined;
-    /** 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 parameter example: ['keyword_data.keyword_info.competition,desc'] default rule: ['keyword_data.keyword_info.search_volume,desc'] 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: ['keyword_data.keyword_info.search_volume,desc','keyword_data.keyword_info.cpc,desc'] */
+    /** *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 parameter             example:             `['keyword_data.keyword_info.competition,desc']`             default rule:             `['keyword_data.keyword_info.search_volume,desc']`             **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:             `['keyword_data.keyword_info.search_volume,desc','keyword_data.keyword_info.cpc,desc']` */
     order_by?: string[] | undefined;
-    /** 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 */
+    /** *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 */
     tag?: string | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleDomainIntersectionLiveRequestInfo implements IDataforseoLabsGoogleDomainIntersectionLiveRequestInfo {
-    /** domain required field the domain name of the first target website the domain should be specified without https:// and www. */
+    /** *domain*             **required field**             the domain name of the first target website             the domain should be specified without `https://` and `www.` */
     target_1?: string | undefined;
-    /** domain required field the domain name of the second target website the domain should be specified without https:// and www. */
+    /** *domain*             **required field**             the domain name of the second target website             the domain should be specified without `https://` and `www.` */
     target_2?: string | undefined;
-    /** full name of the location required field if you don’t specify location_code Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: United Kingdom */
+    /** *full name of the location*             **required field if you don't specify** `location_code`             **Note:** it is required to specify either `location_name` or `location_code`             you can receive the list of available locations with their `location_name` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `United Kingdom` */
     location_name?: string | undefined;
-    /** location code required field if you don’t specify location_name Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: 2840 */
+    /** *location code*             **required field if you don't specify** `location_name`             **Note:** it is required to specify either `location_name` or `location_code`             you can receive the list of available locations with their `location_code` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `2840` */
     location_code?: number | undefined;
-    /** full name of the language required field if you don’t specify language_code Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: English */
+    /** *full name of the language*             **required field if you don't specify** `language_code`             **Note:** it is required to specify either `language_name` or `language_code`             you can receive the list of available languages with their `language_name` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `English` */
     language_name?: string | undefined;
-    /** language code required field if you don’t specify language_name Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: en */
+    /** *language code*             **required field if you don't specify** `language_name`             **Note:** it is required to specify either `language_name` or `language_code`             you can receive the list of available languages with their `language_code` by making a separate request to the             `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages`             example:             `en` */
     language_code?: string | undefined;
-    /** domain intersections in SERP optional field if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million if you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t; thus, the corresponding SERP elements and other data will be provided for the domain specified as target1only default value: true */
+    /** *domain intersections in SERP*             optional field             if you set intersections to `true`, you will get the keywords for which both target domains specified as `target1` and `target2` have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array             **Note:** this endpoint will not provide results if the number of intersecting keywords exceeds 10 million             if you specify `intersections: false`, you will get the keywords for which the domain specified as `target1` has results in SERP, and the domain specified as `target2` doesn't;             thus, the corresponding SERP elements and other data will be provided for the domain specified as `target1`only             default value: `true` */
     intersections?: boolean | undefined;
-    /** search results type indicates type of search results included in the response optional field possible values: ['organic', 'paid', 'featured_snippet', 'local_pack'] default value: ['organic', 'paid'] */
+    /** *search results type*             indicates type of search results included in the response             optional field             possible values:             `['organic', 'paid', 'featured_snippet', 'local_pack']`             default value:             `['organic', 'paid']` */
     item_types?: string[] | undefined;
-    /** include data from SERP for each keyword optional field if set to true, we will return a serp_info array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response default value: false */
+    /** *include data from SERP for each keyword*             optional field             if set to `true`, we will return a `serp_info` array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response             default value: `false` */
     include_serp_info?: boolean | undefined;
-    /** include or exclude data from clickstream-based metrics in the result optional field if the parameter is set to true, you will receive clickstream_keyword_info, clickstream_etv, keyword_info_normalized_with_clickstream, and keyword_info_normalized_with_bing fields in the response default value: false with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this help center article */
+    /** *include or exclude data from clickstream-based metrics in the result*             optional field             if the parameter is set to `true`, you will receive `clickstream_keyword_info`, `clickstream_etv`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response             default value: `false`             with this parameter enabled, you will be charged double the price for the request             learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
     include_clickstream_data?: boolean | undefined;
-    /** the maximum number of returned keywords optional field default value: 100 maximum value: 1000 */
+    /** *the maximum number of returned keywords*             optional field             default value: `100`             maximum value: `1000` */
     limit?: number | undefined;
-    /** offset in the items array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
+    /** *offset in the `items` array of returned keywords*             optional field             default value: `0`             if you specify the `10` value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
     offset?: number | undefined;
-    /** 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, match, not_match, ilike, not_ilike, like, not_like you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters example: ['keyword_data.keyword_info.search_volume','in',[100,1000]] [['first_domain_serp_element.etv','>',0],'and',['first_domain_serp_element.description','like','%goat%']] [['keyword_data.keyword_info.search_volume','>',100], 'and', [['first_domain_serp_element.description','like','%goat%'], 'or', ['second_domain_serp_element.type','=','organic']]] for more information about filters, please refer to Dataforseo Labs – Filters or this help center guide */
+    /** *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`, `match`, `not_match`, `ilike`, `not_ilike`, `like`, `not_like`             you can use the `%` operator with `like` and `not_like`, as well as `ilike` and `not_ilike` to match any string of zero or more characters             example:             `['keyword_data.keyword_info.search_volume','in',[100,1000]]`             `[['first_domain_serp_element.etv','>',0],'and',['first_domain_serp_element.description','like','%goat%']]`             `[['keyword_data.keyword_info.search_volume','>',100],                'and',                [['first_domain_serp_element.description','like','%goat%'],                'or',                ['second_domain_serp_element.type','=','organic']]]`             for more information about filters, please refer to [Dataforseo Labs - Filters](/v3/dataforseo_labs/filters) or this [help center guide](https://dataforseo.com/help-center/how-to-use-filters-in-dataforseo-labs-api) */
     filters?: any[] | undefined;
-    /** 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 parameter example: ['keyword_data.keyword_info.competition,desc'] default rule: ['keyword_data.keyword_info.search_volume,desc'] 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: ['keyword_data.keyword_info.search_volume,desc','keyword_data.keyword_info.cpc,desc'] */
+    /** *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 parameter             example:             `['keyword_data.keyword_info.competition,desc']`             default rule:             `['keyword_data.keyword_info.search_volume,desc']`             **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:             `['keyword_data.keyword_info.search_volume,desc','keyword_data.keyword_info.cpc,desc']` */
     order_by?: string[] | undefined;
-    /** 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 */
+    /** *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 */
     tag?: string | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleDomainIntersectionLiveRequestInfo);

package/dist/cjs/models/DataforseoLabsGoogleDomainIntersectionLiveResponseInfo.d.ts

@@ -1,12 +1,12 @@
 import { DataforseoLabsGoogleDomainIntersectionLiveTaskInfo } from "./DataforseoLabsGoogleDomainIntersectionLiveTaskInfo";
 import { BaseResponseInfo, IBaseResponseInfo } from "./BaseResponseInfo";
 export interface IDataforseoLabsGoogleDomainIntersectionLiveResponseInfo extends IBaseResponseInfo {
-    /** array of tasks */
+    /** *array of tasks* */
     tasks?: DataforseoLabsGoogleDomainIntersectionLiveTaskInfo[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleDomainIntersectionLiveResponseInfo extends BaseResponseInfo implements IDataforseoLabsGoogleDomainIntersectionLiveResponseInfo {
-    /** array of tasks */
+    /** *array of tasks* */
     tasks?: DataforseoLabsGoogleDomainIntersectionLiveTaskInfo[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleDomainIntersectionLiveResponseInfo);

package/dist/cjs/models/DataforseoLabsGoogleDomainIntersectionLiveResultInfo.d.ts

@@ -1,39 +1,39 @@
 import { DataforseoLabsGoogleDomainIntersectionLiveItem } from "./DataforseoLabsGoogleDomainIntersectionLiveItem";
 export interface IDataforseoLabsGoogleDomainIntersectionLiveResultInfo {
-    /** search engine type */
+    /** *search engine type* */
     se_type?: string | undefined;
-    /** the first target domain in a POST array */
+    /** *the first target domain in a POST array* */
     target_1?: string | undefined;
-    /** the second target domain in a POST array */
+    /** *the second target domain in a POST array* */
     target_2?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** total amount of results in our database relevant to your request */
+    /** *total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** contains keywords, relevant SERP elements and related data */
+    /** *contains keywords, relevant SERP elements and related data* */
     items?: DataforseoLabsGoogleDomainIntersectionLiveItem[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleDomainIntersectionLiveResultInfo implements IDataforseoLabsGoogleDomainIntersectionLiveResultInfo {
-    /** search engine type */
+    /** *search engine type* */
     se_type?: string | undefined;
-    /** the first target domain in a POST array */
+    /** *the first target domain in a POST array* */
     target_1?: string | undefined;
-    /** the second target domain in a POST array */
+    /** *the second target domain in a POST array* */
     target_2?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** total amount of results in our database relevant to your request */
+    /** *total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** contains keywords, relevant SERP elements and related data */
+    /** *contains keywords, relevant SERP elements and related data* */
     items?: DataforseoLabsGoogleDomainIntersectionLiveItem[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleDomainIntersectionLiveResultInfo);

package/dist/cjs/models/DataforseoLabsGoogleDomainIntersectionLiveTaskInfo.d.ts

@@ -1,12 +1,12 @@
 import { DataforseoLabsGoogleDomainIntersectionLiveResultInfo } from "./DataforseoLabsGoogleDomainIntersectionLiveResultInfo";
 import { BaseResponseTaskInfo, IBaseResponseTaskInfo } from "./BaseResponseTaskInfo";
 export interface IDataforseoLabsGoogleDomainIntersectionLiveTaskInfo extends IBaseResponseTaskInfo {
-    /** array of results */
+    /** *array of results* */
     result?: DataforseoLabsGoogleDomainIntersectionLiveResultInfo[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleDomainIntersectionLiveTaskInfo extends BaseResponseTaskInfo implements IDataforseoLabsGoogleDomainIntersectionLiveTaskInfo {
-    /** array of results */
+    /** *array of results* */
     result?: DataforseoLabsGoogleDomainIntersectionLiveResultInfo[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleDomainIntersectionLiveTaskInfo);

package/dist/cjs/models/DataforseoLabsGoogleHistoricalSerpsLiveItem.d.ts

@@ -1,60 +1,60 @@
 import { SpellInfo } from "./SpellInfo";
 import { BaseDataforseoLabsApiElementItem } from "./BaseDataforseoLabsApiElementItem";
 export interface IDataforseoLabsGoogleHistoricalSerpsLiveItem {
-    /** search engine type in a POST array */
+    /** *search engine type in a POST array* */
     se_type?: string | undefined;
-    /** keyword received in a POST array the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character) */
+    /** *keyword received in a POST array*             **the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character)** */
     keyword?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** search engine domain in a POST array */
+    /** *search engine domain in a POST array* */
     se_domain?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** direct URL to search engine results you can use it to make sure that we provided accurate results */
+    /** *direct URL to search engine results*             you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received*             in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00”             example:             `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** autocorrection of the search engine if the search engine provided results for a keyword that was corrected, we will specify the keyword corrected by the search engine and the type of autocorrection */
+    /** *autocorrection of the search engine*             if the search engine provided results for a keyword that was corrected, we will specify the keyword corrected by the search engine and the type of autocorrection */
     spell?: SpellInfo | undefined;
-    /** types of search results in SERP contains types of search results (items) found in SERP. possible item types: answer_box, carousel, multi_carousel, featured_snippet, google_flights, google_reviews, google_posts, images, jobs, knowledge_graph, local_pack, hotels_pack, map, organic, paid, people_also_ask, related_searches, people_also_search, shopping, top_stories, twitter, video, events, mention_carousel, recipes, top_sights, scholarly_articles, popular_products, podcasts, questions_and_answers, find_results_on, stocks_box, visual_stories, commercial_units,  local_services, google_hotels, math_solver, ai_overview */
+    /** *types of search results in SERP*             contains types of search results (`items`) found in SERP.             possible item types:             [answer_box](#answer_box), [carousel](#carousel), [multi_carousel](#multi_carousel), [featured_snippet](#featured_snippet), [google_flights](#google_flights), [google_reviews](#google_reviews), [google_posts](#google_posts), [images](#images), [jobs](#jobs), [knowledge_graph](#knowledge_graph), [local_pack](#local_pack), [hotels_pack](#hotels_pack), [map](#map), [organic](#organic), [paid](#paid), [people_also_ask](#people_also_ask), [related_searches](#related_searches), [people_also_search](#people_also_search), [shopping](#shopping), [top_stories](#top_stories), [twitter](#twitter), [video](#video), [events](#events), [mention_carousel](#mention_carousel), [recipes](#recipes), [top_sights](#top_sights), [scholarly_articles](#scholarly_articles), [popular_products](#popular_products), [podcasts](#podcasts), [questions_and_answers](#questions_and_answers), [find_results_on](#find_results_on), [stocks_box](#stocks_box), [visual_stories](#visual_stories), [commercial_units](#commercial_units),  [local_services](#local_services), [google_hotels](#google_hotels), [math_solver](#math_solver), [ai_overview](#ai_overview) */
     item_types?: string[] | undefined;
-    /** total number of results in SERP */
+    /** *total number of results in SERP* */
     se_results_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** historical SERPs and related data found in the database */
+    /** *historical SERPs and related data found in the database* */
     items?: BaseDataforseoLabsApiElementItem[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleHistoricalSerpsLiveItem implements IDataforseoLabsGoogleHistoricalSerpsLiveItem {
-    /** search engine type in a POST array */
+    /** *search engine type in a POST array* */
     se_type?: string | undefined;
-    /** keyword received in a POST array the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character) */
+    /** *keyword received in a POST array*             **the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character)** */
     keyword?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** search engine domain in a POST array */
+    /** *search engine domain in a POST array* */
     se_domain?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** direct URL to search engine results you can use it to make sure that we provided accurate results */
+    /** *direct URL to search engine results*             you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received*             in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00”             example:             `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** autocorrection of the search engine if the search engine provided results for a keyword that was corrected, we will specify the keyword corrected by the search engine and the type of autocorrection */
+    /** *autocorrection of the search engine*             if the search engine provided results for a keyword that was corrected, we will specify the keyword corrected by the search engine and the type of autocorrection */
     spell?: SpellInfo | undefined;
-    /** types of search results in SERP contains types of search results (items) found in SERP. possible item types: answer_box, carousel, multi_carousel, featured_snippet, google_flights, google_reviews, google_posts, images, jobs, knowledge_graph, local_pack, hotels_pack, map, organic, paid, people_also_ask, related_searches, people_also_search, shopping, top_stories, twitter, video, events, mention_carousel, recipes, top_sights, scholarly_articles, popular_products, podcasts, questions_and_answers, find_results_on, stocks_box, visual_stories, commercial_units,  local_services, google_hotels, math_solver, ai_overview */
+    /** *types of search results in SERP*             contains types of search results (`items`) found in SERP.             possible item types:             [answer_box](#answer_box), [carousel](#carousel), [multi_carousel](#multi_carousel), [featured_snippet](#featured_snippet), [google_flights](#google_flights), [google_reviews](#google_reviews), [google_posts](#google_posts), [images](#images), [jobs](#jobs), [knowledge_graph](#knowledge_graph), [local_pack](#local_pack), [hotels_pack](#hotels_pack), [map](#map), [organic](#organic), [paid](#paid), [people_also_ask](#people_also_ask), [related_searches](#related_searches), [people_also_search](#people_also_search), [shopping](#shopping), [top_stories](#top_stories), [twitter](#twitter), [video](#video), [events](#events), [mention_carousel](#mention_carousel), [recipes](#recipes), [top_sights](#top_sights), [scholarly_articles](#scholarly_articles), [popular_products](#popular_products), [podcasts](#podcasts), [questions_and_answers](#questions_and_answers), [find_results_on](#find_results_on), [stocks_box](#stocks_box), [visual_stories](#visual_stories), [commercial_units](#commercial_units),  [local_services](#local_services), [google_hotels](#google_hotels), [math_solver](#math_solver), [ai_overview](#ai_overview) */
     item_types?: string[] | undefined;
-    /** total number of results in SERP */
+    /** *total number of results in SERP* */
     se_results_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** historical SERPs and related data found in the database */
+    /** *historical SERPs and related data found in the database* */
     items?: BaseDataforseoLabsApiElementItem[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleHistoricalSerpsLiveItem);

package/dist/cjs/models/DataforseoLabsGoogleHistoricalSerpsLiveRequestInfo.d.ts

@@ -1,38 +1,38 @@
 export interface IDataforseoLabsGoogleHistoricalSerpsLiveRequestInfo {
-    /** keyword required field you can specify up to 700 characters in the keyword field; all %## will be decoded (plus character ‘+’ will be decoded to a space character); if you need to use the “%” character for your keyword, please specify it as “%25”; if you need to use the “+” character for your keyword, please specify it as “%2B” */
+    /** *keyword* **required field** you can specify **up to 700 characters** in the `keyword` field; all %## will be decoded (plus character ‘+’ will be decoded to a space character); if you need to use the “%” character for your `keyword`, please specify it as “%25”; if you need to use the “+” character for your `keyword`, please specify it as “%2B” */
     keyword?: string | undefined;
-    /** starting date of the time range optional field if you don’t specify this field, the API will return all SERPs collected for 365 days starting from the current datetime value; minimal possible value: 365 days from the current datetime value; date format: 'yyyy-mm-dd' */
+    /** *starting date of the time range* optional field if you don't specify this field, the API will return all SERPs collected for 365 days starting from the current `datetime` value; minimal possible value: 365 days from the current `datetime` value; date format: `'yyyy-mm-dd'` */
     date_from?: string | undefined;
-    /** 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: '2021-09-01' */
+    /** *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: `'2021-09-01'` */
     date_to?: string | undefined;
-    /** full name of the location required field if you don’t specify location_code Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_name by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: United Kingdom */
+    /** *full name of the location* **required field if you don't specify** `location_code` **Note:** it is required to specify either `location_name` or `location_code` you can receive the list of available locations with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `United Kingdom` */
     location_name?: string | undefined;
-    /** unique location identifier required field if you don’t specify location_name Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_code by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: 2840 */
+    /** *unique location identifier* **required field if you don't specify** `location_name` **Note:** it is required to specify either `location_name` or `location_code` you can receive the list of available locations with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `2840` */
     location_code?: number | undefined;
-    /** full name of the language required field if you don’t specify language_code Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_name parameters by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: English */
+    /** *full name of the language* **required field if you don't specify** `language_code` **Note:** it is required to specify either `language_name` or `language_code` you can receive the list of available languages with their `language_name` parameters by making a separate request to the  `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `English` */
     language_name?: string | undefined;
-    /** unique language identifier required field if you don’t specify language_name Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_code parameters by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: en */
+    /** *unique language identifier* **required field if you don't specify** `language_name` **Note:** it is required to specify either `language_name` or `language_code` you can receive the list of available languages with their `language_code` parameters by making a separate request to the  `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `en` */
     language_code?: string | undefined;
-    /** 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 */
+    /** *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 */
     tag?: string | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleHistoricalSerpsLiveRequestInfo implements IDataforseoLabsGoogleHistoricalSerpsLiveRequestInfo {
-    /** keyword required field you can specify up to 700 characters in the keyword field; all %## will be decoded (plus character ‘+’ will be decoded to a space character); if you need to use the “%” character for your keyword, please specify it as “%25”; if you need to use the “+” character for your keyword, please specify it as “%2B” */
+    /** *keyword* **required field** you can specify **up to 700 characters** in the `keyword` field; all %## will be decoded (plus character ‘+’ will be decoded to a space character); if you need to use the “%” character for your `keyword`, please specify it as “%25”; if you need to use the “+” character for your `keyword`, please specify it as “%2B” */
     keyword?: string | undefined;
-    /** starting date of the time range optional field if you don’t specify this field, the API will return all SERPs collected for 365 days starting from the current datetime value; minimal possible value: 365 days from the current datetime value; date format: 'yyyy-mm-dd' */
+    /** *starting date of the time range* optional field if you don't specify this field, the API will return all SERPs collected for 365 days starting from the current `datetime` value; minimal possible value: 365 days from the current `datetime` value; date format: `'yyyy-mm-dd'` */
     date_from?: string | undefined;
-    /** 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: '2021-09-01' */
+    /** *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: `'2021-09-01'` */
     date_to?: string | undefined;
-    /** full name of the location required field if you don’t specify location_code Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_name by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: United Kingdom */
+    /** *full name of the location* **required field if you don't specify** `location_code` **Note:** it is required to specify either `location_name` or `location_code` you can receive the list of available locations with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `United Kingdom` */
     location_name?: string | undefined;
-    /** unique location identifier required field if you don’t specify location_name Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_code by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: 2840 */
+    /** *unique location identifier* **required field if you don't specify** `location_name` **Note:** it is required to specify either `location_name` or `location_code` you can receive the list of available locations with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `2840` */
     location_code?: number | undefined;
-    /** full name of the language required field if you don’t specify language_code Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_name parameters by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: English */
+    /** *full name of the language* **required field if you don't specify** `language_code` **Note:** it is required to specify either `language_name` or `language_code` you can receive the list of available languages with their `language_name` parameters by making a separate request to the  `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `English` */
     language_name?: string | undefined;
-    /** unique language identifier required field if you don’t specify language_name Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_code parameters by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages example: en */
+    /** *unique language identifier* **required field if you don't specify** `language_name` **Note:** it is required to specify either `language_name` or `language_code` you can receive the list of available languages with their `language_code` parameters by making a separate request to the  `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` example: `en` */
     language_code?: string | undefined;
-    /** 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 */
+    /** *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 */
     tag?: string | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleHistoricalSerpsLiveRequestInfo);

package/dist/cjs/models/DataforseoLabsGoogleHistoricalSerpsLiveResponseInfo.d.ts

@@ -1,12 +1,12 @@
 import { DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo } from "./DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo";
 import { BaseResponseInfo, IBaseResponseInfo } from "./BaseResponseInfo";
 export interface IDataforseoLabsGoogleHistoricalSerpsLiveResponseInfo extends IBaseResponseInfo {
-    /** array of tasks */
+    /** *array of tasks* */
     tasks?: DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleHistoricalSerpsLiveResponseInfo extends BaseResponseInfo implements IDataforseoLabsGoogleHistoricalSerpsLiveResponseInfo {
-    /** array of tasks */
+    /** *array of tasks* */
     tasks?: DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleHistoricalSerpsLiveResponseInfo);

package/dist/cjs/models/DataforseoLabsGoogleHistoricalSerpsLiveResultInfo.d.ts

@@ -1,35 +1,35 @@
 import { DataforseoLabsGoogleHistoricalSerpsLiveItem } from "./DataforseoLabsGoogleHistoricalSerpsLiveItem";
 export interface IDataforseoLabsGoogleHistoricalSerpsLiveResultInfo {
-    /** search engine type in a POST array */
+    /** *search engine type in a POST array* */
     se_type?: string | undefined;
-    /** keyword received in a POST array the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character) */
+    /** *keyword received in a POST array*             **the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character)** */
     keyword?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** the total amount of results in our database relevant to your request */
+    /** *the total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** historical SERPs and related data found in the database */
+    /** *historical SERPs and related data found in the database* */
     items?: DataforseoLabsGoogleHistoricalSerpsLiveItem[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleHistoricalSerpsLiveResultInfo implements IDataforseoLabsGoogleHistoricalSerpsLiveResultInfo {
-    /** search engine type in a POST array */
+    /** *search engine type in a POST array* */
     se_type?: string | undefined;
-    /** keyword received in a POST array the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character) */
+    /** *keyword received in a POST array*             **the keyword is returned with decoded %## (plus character ‘+’ will be decoded to a space character)** */
     keyword?: string | undefined;
-    /** location code in a POST array */
+    /** *location code in a POST array* */
     location_code?: number | undefined;
-    /** language code in a POST array */
+    /** *language code in a POST array* */
     language_code?: string | undefined;
-    /** the total amount of results in our database relevant to your request */
+    /** *the total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
-    /** historical SERPs and related data found in the database */
+    /** *historical SERPs and related data found in the database* */
     items?: DataforseoLabsGoogleHistoricalSerpsLiveItem[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleHistoricalSerpsLiveResultInfo);

package/dist/cjs/models/DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo.d.ts

@@ -1,12 +1,12 @@
 import { DataforseoLabsGoogleHistoricalSerpsLiveResultInfo } from "./DataforseoLabsGoogleHistoricalSerpsLiveResultInfo";
 import { BaseResponseTaskInfo, IBaseResponseTaskInfo } from "./BaseResponseTaskInfo";
 export interface IDataforseoLabsGoogleHistoricalSerpsLiveTaskInfo extends IBaseResponseTaskInfo {
-    /** array of results the array includes objects with SERPs for each month within the specified time frame */
+    /** *array of results*             the array includes objects with SERPs for each month within the specified time frame */
     result?: DataforseoLabsGoogleHistoricalSerpsLiveResultInfo[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleHistoricalSerpsLiveTaskInfo extends BaseResponseTaskInfo implements IDataforseoLabsGoogleHistoricalSerpsLiveTaskInfo {
-    /** array of results the array includes objects with SERPs for each month within the specified time frame */
+    /** *array of results*             the array includes objects with SERPs for each month within the specified time frame */
     result?: DataforseoLabsGoogleHistoricalSerpsLiveResultInfo[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGoogleHistoricalSerpsLiveTaskInfo);

package/dist/cjs/models/DataforseoLabsGoogleKeywordIdeasLiveRequestInfo.d.ts

@@ -15,7 +15,7 @@ export interface IDataforseoLabsGoogleKeywordIdeasLiveRequestInfo {
     ignore_synonyms?: boolean | undefined;
     /** *include data from SERP for each keyword* optional field if set to `true`, we will return a `serp_info` array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response default value: `false` */
     include_serp_info?: boolean | undefined;
-    /** *include or exclude data from clickstream-based metrics in the result* optional field if the parameter is set to_`true`, you will receive `clickstream_keyword_info`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response default value: `false` with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them)n */
+    /** *include or exclude data from clickstream-based metrics in the result* optional field if the parameter is set to `true`, you will receive `clickstream_keyword_info`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response default value: `false` with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
     include_clickstream_data?: boolean | undefined;
     /** *the maximum number of keywords in the results array* optional field default value: `700` maximum value: `1000` */
     limit?: number | undefined;
@@ -48,7 +48,7 @@ export declare class DataforseoLabsGoogleKeywordIdeasLiveRequestInfo implements
     ignore_synonyms?: boolean | undefined;
     /** *include data from SERP for each keyword* optional field if set to `true`, we will return a `serp_info` array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response default value: `false` */
     include_serp_info?: boolean | undefined;
-    /** *include or exclude data from clickstream-based metrics in the result* optional field if the parameter is set to_`true`, you will receive `clickstream_keyword_info`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response default value: `false` with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them)n */
+    /** *include or exclude data from clickstream-based metrics in the result* optional field if the parameter is set to `true`, you will receive `clickstream_keyword_info`, `keyword_info_normalized_with_clickstream`, and `keyword_info_normalized_with_bing` fields in the response default value: `false` with this parameter enabled, you will be charged double the price for the request learn more about how clickstream-based metrics are calculated in this [help center article](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
     include_clickstream_data?: boolean | undefined;
     /** *the maximum number of keywords in the results array* optional field default value: `700` maximum value: `1000` */
     limit?: number | undefined;

package/dist/cjs/models/DataforseoLabsGooglePageIntersectionLiveItem.d.ts

@@ -1,22 +1,22 @@
 import { KeywordDataInfo } from "./KeywordDataInfo";
 import { BaseDataforseoLabsApiElementItem } from "./BaseDataforseoLabsApiElementItem";
 export interface IDataforseoLabsGooglePageIntersectionLiveItem {
-    /** search engine type */
+    /** *search engine type* */
     se_type?: string | undefined;
-    /** keyword data for the returned keyword */
+    /** *keyword data for the returned keyword* */
     keyword_data?: KeywordDataInfo | undefined;
-    /** contains data on the SERP elements found for the returned keyword data will be provided in separate arrays for each URL you specified in the pages object when setting a task; depending on the number of specified URLs, it can contain from 1 to 20 arrays named respectively */
+    /** *contains data on the SERP elements found for the returned `keyword`* data will be provided in separate arrays for each URL you specified in the `pages` object when setting a task; depending on the number of specified URLs, it can contain from 1 to 20 arrays named respectively */
     intersection_result?: {
         [key: string]: BaseDataforseoLabsApiElementItem;
     } | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGooglePageIntersectionLiveItem implements IDataforseoLabsGooglePageIntersectionLiveItem {
-    /** search engine type */
+    /** *search engine type* */
     se_type?: string | undefined;
-    /** keyword data for the returned keyword */
+    /** *keyword data for the returned keyword* */
     keyword_data?: KeywordDataInfo | undefined;
-    /** contains data on the SERP elements found for the returned keyword data will be provided in separate arrays for each URL you specified in the pages object when setting a task; depending on the number of specified URLs, it can contain from 1 to 20 arrays named respectively */
+    /** *contains data on the SERP elements found for the returned `keyword`* data will be provided in separate arrays for each URL you specified in the `pages` object when setting a task; depending on the number of specified URLs, it can contain from 1 to 20 arrays named respectively */
     intersection_result?: {
         [key: string]: BaseDataforseoLabsApiElementItem;
     } | undefined;