dataforseo-client 2.1.6 → 2.1.8

package/dist/esm/models/DataforseoLabsGooglePageIntersectionLiveRequestInfo.d.ts

@@ -1,78 +1,78 @@
 export interface IDataforseoLabsGooglePageIntersectionLiveRequestInfo {
-    /** *target URLs of pages* **required field** you can set **up to 20 pages** in this object the pages should be specified with absolute URLs (including http:// or https://) example: `'pages': {` `'1':'https://www.apple.com/mac/*',` `'2':'https://dataforseo.com/*',` `'3':'https://support.microsoft.com/'` `}`if you specify a single page here, we will return results only for this page; you can also use a wildcard ('*') character to specify the search pattern example: `'example.com'` search for the exact URL `'example.com/eng/*'` search for the *example.com* page and all its related URLs which start with *'/eng/'*, such as *'example.com/eng/index.html'* and *'example.com/eng/help/'*, etc. **note:** a wilcard should be placed after the slash ('/') character in the end of the URL, it is **not possible** to place it after the domain in the following way: `https://dataforseo.com`***** use `https://dataforseo.com`** /*** instead **Note:** this endpoint will not provide results if the number of intersecting keywords exceeds 10 million */
+    /** target URLs of pagesrequired fieldyou can set up to 20 pages in this objectthe pages should be specified with absolute URLs (including http:// or https://)example:'pages': {'1':'https://www.apple.com/mac/*','2':'https://dataforseo.com/*','3':'https://support.microsoft.com/'}if you specify a single page here, we will return results only for this page;you can also use a wildcard ('') character to specify the search patternexample:'example.com'search for the exact URL'example.com/eng/'search for the example.com page and all its related URLs which start with '/eng/', such as 'example.com/eng/index.html' and 'example.com/eng/help/', etc.note: a wilcard should be placed after the slash ('/') character in the end of the URL, it is not possible to place it after the domain in the following way:https://dataforseo.comuse https://dataforseo.com/ insteadNote: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million */
     pages?: {
         [key: string]: string;
     } | undefined;
-    /** *URLs of pages you want to exclude* optional field you can set **up to 10 pages** in this array if you use this array, results will contain the keywords for which URLs from the `pages` object rank, but URLs from `exclude_pages` array do not; **note** that if you specify this field, the results will be based on the keywords **any** URL from `pages` ranks for regardless of intersections between them. However, you can set `intersection_mode` to `intersect` and results will contain the keywords **all** URLs from `pages` rank for in the same SERP and URLs from `exclude_pages` do not.  use a wildcard ('*') character to specify the search pattern example: `'exclude_pages':` `['https://www.apple.com/iphone/*',` `'https://dataforseo.com/apis/*',` `'https://www.microsoft.com/en-us/industry/services/']` */
+    /** URLs of pages you want to excludeoptional fieldyou can set up to 10 pages in this arrayif you use this array, results will contain the keywords for which URLs from the pages object rank, but URLs from exclude_pages array do not;note that if you specify this field, the results will be based on the keywords any URL from pages ranks for regardless of intersections between them. However, you can set intersection_mode to intersect and results will contain the keywords all URLs from pages rank for in the same SERP and URLs from exclude_pages do not. use a wildcard ('*') character to specify the search patternexample:'exclude_pages':['https://www.apple.com/iphone/*','https://dataforseo.com/apis/*','https://www.microsoft.com/en-us/industry/services/'] */
     exclude_pages?: 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 locationrequired field if you don't specify location_codeNote: it is required to specify either location_name or location_codeyou 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_languagesexample: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 coderequired field if you don't specify location_nameNote: it is required to specify either location_name or location_codeyou 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_languagesexample: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 languagerequired field if you don't specify language_codeNote: it is required to specify either language_name or language_codeyou 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_languagesexample: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 coderequired field if you don't specify language_nameNote: it is required to specify either language_name or language_codeyou 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_languagesexample:en */
     language_code?: string | 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 typeindicates type of search results included in the responseoptional fieldpossible values: ['organic', 'paid', 'featured_snippet', 'local_pack']default value: ['organic', 'paid'] */
     item_types?: string[] | undefined;
-    /** *the maximum number of returned keywords* optional field default value: `100` maximum value: `1000` */
+    /** the maximum number of returned keywordsoptional fielddefault value: 100maximum value: 1000 */
     limit?: number | undefined;
-    /** *offset in the `items` array of returned keywords* optional field default value: `0` if you specify `10` here, 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 keywordsoptional fielddefault value: 0if you specify 10 here, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
     offset?: number | undefined;
-    /** *indicates if the subdomains will be included in the search* optional field if set to `false`, the subdomains will be ignored default value: `true` */
+    /** indicates if the subdomains will be included in the searchoptional fieldif set to false, the subdomains will be ignoreddefault value: true */
     include_subdomains?: boolean | undefined;
-    /** *indicates whether to intersect keywords* optional field use this field to intersect or merge results for the specified URLs possible values: `union`, `intersect` `union` - results are based on all keywords **any** URL from `pages` rank for; `intersect` - results are based on the keywords **all** URLs from `pages` rank for in the same SERP: by default, results are based on the `intersect` mode if you specify only `pages` array. If you specify `exclude_pages` as well, results are based on the `union` mode */
+    /** indicates whether to intersect keywordsoptional fielduse this field to intersect or merge results for the specified URLspossible values: union, intersectunion - results are based on all keywords any URL from pages rank for;intersect - results are based on the keywords all URLs from pages rank for in the same SERP:by default, results are based on the intersect mode if you specify only pages array. If you specify exclude_pages as well, results are based on the union mode */
     intersection_mode?: 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 keywordoptional fieldif 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 responsedefault 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](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
+    /** include or exclude data from clickstream-based metrics in the resultoptional fieldif 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 responsedefault value: falsewith this parameter enabled, you will be charged double the price for the requestlearn more about how clickstream-based metrics are calculated in this help center article */
     include_clickstream_data?: boolean | undefined;
-    /** *ignore highly similar keywords* optional field if set to `true` only core keywords will be returned, all highly similar keywords will be excluded;   default value: `false` */
+    /** ignore highly similar keywordsoptional fieldif set to true only core keywords will be returned, all highly similar keywords will be excluded;  default value: false */
     ignore_synonyms?: boolean | 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`, `ilike`, `not_ilike`, `like`, `not_like`, `match`, `not_match` 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 **note** that if you want to filter by any field in the `intersection_result` array you need to specify the number of corresponding page for instance, if you want to filter results by the ranking of the first specified URL, you should set the following filter: `[intersection_result.1.rank_absolute,'=',1]` if you want to filter results and receive only organic listings for the third specified URL, you should set the following filter: `[intersection_result.3.type,'=','organic']` , etc.example: `['keyword_data.keyword_info.search_volume','in',[100,1000]]` `[['intersection_result.1.etv','>',0],'and',['intersection_result.1.description','like','%goat%']]``[['keyword_data.keyword_info.search_volume','>',100],'and',[['intersection_result.2.description','like','%goat%'],'or',['intersection_result.2.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) */
+    /** array of results filtering parametersoptional fieldyou can add several filters at once (8 filters maximum)you should set a logical operator and, or between the conditionsthe following operators are supported:regex, not_regex, , >=, =, <>, in, not_in, ilike, not_ilike, like, not_like, match, not_matchyou can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more charactersnote that if you want to filter by any field in the intersection_result array you need to specify the number of corresponding pagefor instance, if you want to filter results by the ranking of the first specified URL, you should set the following filter:[intersection_result.1.rank_absolute,'=',1]if you want to filter results and receive only organic listings for the third specified URL, you should set the following filter:[intersection_result.3.type,'=','organic'] , etc.example:['keyword_data.keyword_info.search_volume','in',[100,1000]][['intersection_result.1.etv','>',0],'and',['intersection_result.1.description','like','%goat%']][['keyword_data.keyword_info.search_volume','>',100],'and',[['intersection_result.2.description','like','%goat%'],'or',['intersection_result.2.type','=','organic']]]for more information about filters, please refer to Dataforseo Labs - Filters or this help center guide */
     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: `['intersection_result.1.rank_group,asc','intersection_result.2.rank_absolute,asc']` */
+    /** results sorting rulesoptional fieldyou can use the same values as in the filters array to sort the resultspossible sorting types:asc - results will be sorted in the ascending orderdesc - results will be sorted in the descending orderyou should use a comma to set up a sorting parameterexample:['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 requestyou should use a comma to separate several sorting rulesexample:['intersection_result.1.rank_group,asc','intersection_result.2.rank_absolute,asc'] */
     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 identifieroptional fieldthe character limit is 255you can use this parameter to identify the task and match it with the resultyou will find the specified tag value in the data object of the response */
     tag?: string | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGooglePageIntersectionLiveRequestInfo implements IDataforseoLabsGooglePageIntersectionLiveRequestInfo {
-    /** *target URLs of pages* **required field** you can set **up to 20 pages** in this object the pages should be specified with absolute URLs (including http:// or https://) example: `'pages': {` `'1':'https://www.apple.com/mac/*',` `'2':'https://dataforseo.com/*',` `'3':'https://support.microsoft.com/'` `}`if you specify a single page here, we will return results only for this page; you can also use a wildcard ('*') character to specify the search pattern example: `'example.com'` search for the exact URL `'example.com/eng/*'` search for the *example.com* page and all its related URLs which start with *'/eng/'*, such as *'example.com/eng/index.html'* and *'example.com/eng/help/'*, etc. **note:** a wilcard should be placed after the slash ('/') character in the end of the URL, it is **not possible** to place it after the domain in the following way: `https://dataforseo.com`***** use `https://dataforseo.com`** /*** instead **Note:** this endpoint will not provide results if the number of intersecting keywords exceeds 10 million */
+    /** target URLs of pagesrequired fieldyou can set up to 20 pages in this objectthe pages should be specified with absolute URLs (including http:// or https://)example:'pages': {'1':'https://www.apple.com/mac/*','2':'https://dataforseo.com/*','3':'https://support.microsoft.com/'}if you specify a single page here, we will return results only for this page;you can also use a wildcard ('') character to specify the search patternexample:'example.com'search for the exact URL'example.com/eng/'search for the example.com page and all its related URLs which start with '/eng/', such as 'example.com/eng/index.html' and 'example.com/eng/help/', etc.note: a wilcard should be placed after the slash ('/') character in the end of the URL, it is not possible to place it after the domain in the following way:https://dataforseo.comuse https://dataforseo.com/ insteadNote: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million */
     pages?: {
         [key: string]: string;
     } | undefined;
-    /** *URLs of pages you want to exclude* optional field you can set **up to 10 pages** in this array if you use this array, results will contain the keywords for which URLs from the `pages` object rank, but URLs from `exclude_pages` array do not; **note** that if you specify this field, the results will be based on the keywords **any** URL from `pages` ranks for regardless of intersections between them. However, you can set `intersection_mode` to `intersect` and results will contain the keywords **all** URLs from `pages` rank for in the same SERP and URLs from `exclude_pages` do not.  use a wildcard ('&ast;') character to specify the search pattern example: `'exclude_pages':` `['https://www.apple.com/iphone/&ast;',` `'https://dataforseo.com/apis/&ast;',` `'https://www.microsoft.com/en-us/industry/services/']` */
+    /** URLs of pages you want to excludeoptional fieldyou can set up to 10 pages in this arrayif you use this array, results will contain the keywords for which URLs from the pages object rank, but URLs from exclude_pages array do not;note that if you specify this field, the results will be based on the keywords any URL from pages ranks for regardless of intersections between them. However, you can set intersection_mode to intersect and results will contain the keywords all URLs from pages rank for in the same SERP and URLs from exclude_pages do not. use a wildcard ('*') character to specify the search patternexample:'exclude_pages':['https://www.apple.com/iphone/*','https://dataforseo.com/apis/*','https://www.microsoft.com/en-us/industry/services/'] */
     exclude_pages?: 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 locationrequired field if you don't specify location_codeNote: it is required to specify either location_name or location_codeyou 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_languagesexample: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 coderequired field if you don't specify location_nameNote: it is required to specify either location_name or location_codeyou 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_languagesexample: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 languagerequired field if you don't specify language_codeNote: it is required to specify either language_name or language_codeyou 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_languagesexample: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 coderequired field if you don't specify language_nameNote: it is required to specify either language_name or language_codeyou 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_languagesexample:en */
     language_code?: string | 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 typeindicates type of search results included in the responseoptional fieldpossible values: ['organic', 'paid', 'featured_snippet', 'local_pack']default value: ['organic', 'paid'] */
     item_types?: string[] | undefined;
-    /** *the maximum number of returned keywords* optional field default value: `100` maximum value: `1000` */
+    /** the maximum number of returned keywordsoptional fielddefault value: 100maximum value: 1000 */
     limit?: number | undefined;
-    /** *offset in the `items` array of returned keywords* optional field default value: `0` if you specify `10` here, 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 keywordsoptional fielddefault value: 0if you specify 10 here, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords */
     offset?: number | undefined;
-    /** *indicates if the subdomains will be included in the search* optional field if set to `false`, the subdomains will be ignored default value: `true` */
+    /** indicates if the subdomains will be included in the searchoptional fieldif set to false, the subdomains will be ignoreddefault value: true */
     include_subdomains?: boolean | undefined;
-    /** *indicates whether to intersect keywords* optional field use this field to intersect or merge results for the specified URLs possible values: `union`, `intersect` `union` - results are based on all keywords **any** URL from `pages` rank for; `intersect` - results are based on the keywords **all** URLs from `pages` rank for in the same SERP: by default, results are based on the `intersect` mode if you specify only `pages` array. If you specify `exclude_pages` as well, results are based on the `union` mode */
+    /** indicates whether to intersect keywordsoptional fielduse this field to intersect or merge results for the specified URLspossible values: union, intersectunion - results are based on all keywords any URL from pages rank for;intersect - results are based on the keywords all URLs from pages rank for in the same SERP:by default, results are based on the intersect mode if you specify only pages array. If you specify exclude_pages as well, results are based on the union mode */
     intersection_mode?: 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 keywordoptional fieldif 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 responsedefault 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](https://dataforseo.com/help-center/what-are-clickstream-based-metrics-and-how-do-we-calculate-them) */
+    /** include or exclude data from clickstream-based metrics in the resultoptional fieldif 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 responsedefault value: falsewith this parameter enabled, you will be charged double the price for the requestlearn more about how clickstream-based metrics are calculated in this help center article */
     include_clickstream_data?: boolean | undefined;
-    /** *ignore highly similar keywords* optional field if set to `true` only core keywords will be returned, all highly similar keywords will be excluded;   default value: `false` */
+    /** ignore highly similar keywordsoptional fieldif set to true only core keywords will be returned, all highly similar keywords will be excluded;  default value: false */
     ignore_synonyms?: boolean | 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`, `ilike`, `not_ilike`, `like`, `not_like`, `match`, `not_match` 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 **note** that if you want to filter by any field in the `intersection_result` array you need to specify the number of corresponding page for instance, if you want to filter results by the ranking of the first specified URL, you should set the following filter: `[intersection_result.1.rank_absolute,'=',1]` if you want to filter results and receive only organic listings for the third specified URL, you should set the following filter: `[intersection_result.3.type,'=','organic']` , etc.example: `['keyword_data.keyword_info.search_volume','in',[100,1000]]` `[['intersection_result.1.etv','>',0],'and',['intersection_result.1.description','like','%goat%']]``[['keyword_data.keyword_info.search_volume','>',100],'and',[['intersection_result.2.description','like','%goat%'],'or',['intersection_result.2.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) */
+    /** array of results filtering parametersoptional fieldyou can add several filters at once (8 filters maximum)you should set a logical operator and, or between the conditionsthe following operators are supported:regex, not_regex, , >=, =, <>, in, not_in, ilike, not_ilike, like, not_like, match, not_matchyou can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more charactersnote that if you want to filter by any field in the intersection_result array you need to specify the number of corresponding pagefor instance, if you want to filter results by the ranking of the first specified URL, you should set the following filter:[intersection_result.1.rank_absolute,'=',1]if you want to filter results and receive only organic listings for the third specified URL, you should set the following filter:[intersection_result.3.type,'=','organic'] , etc.example:['keyword_data.keyword_info.search_volume','in',[100,1000]][['intersection_result.1.etv','>',0],'and',['intersection_result.1.description','like','%goat%']][['keyword_data.keyword_info.search_volume','>',100],'and',[['intersection_result.2.description','like','%goat%'],'or',['intersection_result.2.type','=','organic']]]for more information about filters, please refer to Dataforseo Labs - Filters or this help center guide */
     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: `['intersection_result.1.rank_group,asc','intersection_result.2.rank_absolute,asc']` */
+    /** results sorting rulesoptional fieldyou can use the same values as in the filters array to sort the resultspossible sorting types:asc - results will be sorted in the ascending orderdesc - results will be sorted in the descending orderyou should use a comma to set up a sorting parameterexample:['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 requestyou should use a comma to separate several sorting rulesexample:['intersection_result.1.rank_group,asc','intersection_result.2.rank_absolute,asc'] */
     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 identifieroptional fieldthe character limit is 255you can use this parameter to identify the task and match it with the resultyou will find the specified tag value in the data object of the response */
     tag?: string | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGooglePageIntersectionLiveRequestInfo);

package/dist/esm/models/DataforseoLabsGooglePageIntersectionLiveResponseInfo.d.ts

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

package/dist/esm/models/DataforseoLabsGooglePageIntersectionLiveResultInfo.d.ts

@@ -1,43 +1,43 @@
 import { DataforseoLabsGooglePageIntersectionLiveItem } from "./DataforseoLabsGooglePageIntersectionLiveItem";
 export interface IDataforseoLabsGooglePageIntersectionLiveResultInfo {
-    /** *search engine type* */
+    /** search engine type */
     se_type?: string | undefined;
-    /** *URLs you specified a POST array* */
+    /** URLs you specified a POST array */
     pages?: {
         [key: string]: string;
     } | undefined;
-    /** *URLs you specified in a POST array that will be excluded from the results* */
+    /** URLs you specified in a POST array that will be excluded from the results */
     exclude_pages?: 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?: DataforseoLabsGooglePageIntersectionLiveItem[] | undefined;
     [key: string]: any;
 }
 export declare class DataforseoLabsGooglePageIntersectionLiveResultInfo implements IDataforseoLabsGooglePageIntersectionLiveResultInfo {
-    /** *search engine type* */
+    /** search engine type */
     se_type?: string | undefined;
-    /** *URLs you specified a POST array* */
+    /** URLs you specified a POST array */
     pages?: {
         [key: string]: string;
     } | undefined;
-    /** *URLs you specified in a POST array that will be excluded from the results* */
+    /** URLs you specified in a POST array that will be excluded from the results */
     exclude_pages?: 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?: DataforseoLabsGooglePageIntersectionLiveItem[] | undefined;
     [key: string]: any;
     constructor(data?: IDataforseoLabsGooglePageIntersectionLiveResultInfo);

package/dist/esm/models/DataforseoLabsGooglePageIntersectionLiveTaskInfo.d.ts

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

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveRequestInfo.d.ts

@@ -1,10 +1,6 @@
 export interface IDataforseoLabsGoogleSearchIntentLiveRequestInfo {
     /** *target keywords* **required field** UTF-8 encoding maximum number of keywords you can specify in this array: 1000; the keywords will be converted to lowercase format learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
-    /** *full name of the language* **required field if don't specify `language_code`** you can receive the list of available languages with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` **Note:** this endpoint currently supports the following languages only: `Arabic`, `ar`, `Chinese(Traditional)`, `zh-TW`, `Czech`, `cs`, `Danish`, `da`, `Dutch`, `nl`, `English`, `en`, `Finnish`, `fi`, `French`, `fr`, `German`, `de`, `Hebrew`, `he`, `Hindi`, `hi`, `Italian`, `it`, `Japanese`, `ja`, `Korean`, `ko`, `Malay`, `ms`, `Norwegian(Bokmål)`, `nb`, `Polish`, `pl`, `Portuguese`, `pt`, `Romanian`, `ro`, `Russian`, `ru`, `Spanish`, `es`, `Swedish`, `sv`, `Thai`, `th`, `Ukrainian`, `uk`, `Vietnamese`, `vi`, `Bulgarian`, `bg`, `Croatian`, `hr`, `Serbian`, `sr`, `Slovenian`, `sl`, `Bosnian`, `bs`, `Greek`, `el`, `Hungarian`, `hu`, `Slovak`, `sk`, `Turkish`, `tr` example: `English` */
-    language_name?: string | undefined;
-    /** *language code* **required field if don't specify `language_name`** you can receive the list of available languages with their `language_code` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` **Note:** this endpoint currently supports [these languages only;](#lng) 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 */
     tag?: string | undefined;
     [key: string]: any;
@@ -12,10 +8,6 @@ export interface IDataforseoLabsGoogleSearchIntentLiveRequestInfo {
 export declare class DataforseoLabsGoogleSearchIntentLiveRequestInfo implements IDataforseoLabsGoogleSearchIntentLiveRequestInfo {
     /** *target keywords* **required field** UTF-8 encoding maximum number of keywords you can specify in this array: 1000; the keywords will be converted to lowercase format learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
-    /** *full name of the language* **required field if don't specify `language_code`** you can receive the list of available languages with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` **Note:** this endpoint currently supports the following languages only: `Arabic`, `ar`, `Chinese(Traditional)`, `zh-TW`, `Czech`, `cs`, `Danish`, `da`, `Dutch`, `nl`, `English`, `en`, `Finnish`, `fi`, `French`, `fr`, `German`, `de`, `Hebrew`, `he`, `Hindi`, `hi`, `Italian`, `it`, `Japanese`, `ja`, `Korean`, `ko`, `Malay`, `ms`, `Norwegian(Bokmål)`, `nb`, `Polish`, `pl`, `Portuguese`, `pt`, `Romanian`, `ro`, `Russian`, `ru`, `Spanish`, `es`, `Swedish`, `sv`, `Thai`, `th`, `Ukrainian`, `uk`, `Vietnamese`, `vi`, `Bulgarian`, `bg`, `Croatian`, `hr`, `Serbian`, `sr`, `Slovenian`, `sl`, `Bosnian`, `bs`, `Greek`, `el`, `Hungarian`, `hu`, `Slovak`, `sk`, `Turkish`, `tr` example: `English` */
-    language_name?: string | undefined;
-    /** *language code* **required field if don't specify `language_name`** you can receive the list of available languages with their `language_code` by making a separate request to `https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages` **Note:** this endpoint currently supports [these languages only;](#lng) 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 */
     tag?: string | undefined;
     [key: string]: any;

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveRequestInfo.js

@@ -14,8 +14,6 @@ export class DataforseoLabsGoogleSearchIntentLiveRequestInfo {
                     this[property] = data[property];
             }
             this.keywords = data["keywords"];
-            this.language_name = data["language_name"];
-            this.language_code = data["language_code"];
             this.tag = data["tag"];
         }
     }
@@ -28,8 +26,6 @@ export class DataforseoLabsGoogleSearchIntentLiveRequestInfo {
     toJSON(data) {
         data = typeof data === 'object' ? data : {};
         data["keywords"] = this.keywords;
-        data["language_name"] = this.language_name;
-        data["language_code"] = this.language_code;
         data["tag"] = this.tag;
         return data;
     }

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveRequestInfo.js.map

@@ -1 +1 @@
-{"version":3,"file":"DataforseoLabsGoogleSearchIntentLiveRequestInfo.js","sourceRoot":"","sources":["../../../src/models/DataforseoLabsGoogleSearchIntentLiveRequestInfo.ts"],"names":[],"mappings":"AAkBA,MAAM,OAAO,+CAA+C;IAyBxD,YAAY,IAAuD;QAEnE,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBACvB,IAAK,CAAC,QAAQ,CAAC,GAAS,IAAK,CAAC,QAAQ,CAAC,CAAC;YACtD,CAAC;QACL,CAAC;IAED,CAAC;IAED,IAAI,CAAC,IAAU;QACX,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBAC7B,IAAI,CAAC,QAAQ,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC,CAAC;YACxC,CAAC;YACD,IAAI,CAAC,QAAQ,GAAG,IAAI,CAAC,UAAU,CAAC,CAAC;YACjC,IAAI,CAAC,aAAa,GAAG,IAAI,CAAC,eAAe,CAAC,CAAC;YAC3C,IAAI,CAAC,aAAa,GAAG,IAAI,CAAC,eAAe,CAAC,CAAC;YAC3C,IAAI,CAAC,GAAG,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACL,CAAC;IAED,MAAM,CAAC,MAAM,CAAC,IAAS;QACnB,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAG5C,IAAI,MAAM,GAAG,IAAI,+CAA+C,EAAE,CAAC;QACnE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAClB,OAAO,MAAM,CAAC;IAClB,CAAC;IAED,MAAM,CAAC,IAAU;QACb,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAI5C,IAAI,CAAC,UAAU,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC;QACjC,IAAI,CAAC,eAAe,CAAC,GAAG,IAAI,CAAC,aAAa,CAAC;QAC3C,IAAI,CAAC,eAAe,CAAC,GAAG,IAAI,CAAC,aAAa,CAAC;QAC3C,IAAI,CAAC,KAAK,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC;QACvB,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}
+{"version":3,"file":"DataforseoLabsGoogleSearchIntentLiveRequestInfo.js","sourceRoot":"","sources":["../../../src/models/DataforseoLabsGoogleSearchIntentLiveRequestInfo.ts"],"names":[],"mappings":"AAYA,MAAM,OAAO,+CAA+C;IAexD,YAAY,IAAuD;QAEnE,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBACvB,IAAK,CAAC,QAAQ,CAAC,GAAS,IAAK,CAAC,QAAQ,CAAC,CAAC;YACtD,CAAC;QACL,CAAC;IAED,CAAC;IAED,IAAI,CAAC,IAAU;QACX,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBAC7B,IAAI,CAAC,QAAQ,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC,CAAC;YACxC,CAAC;YACD,IAAI,CAAC,QAAQ,GAAG,IAAI,CAAC,UAAU,CAAC,CAAC;YACjC,IAAI,CAAC,GAAG,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC;QAC3B,CAAC;IACL,CAAC;IAED,MAAM,CAAC,MAAM,CAAC,IAAS;QACnB,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAG5C,IAAI,MAAM,GAAG,IAAI,+CAA+C,EAAE,CAAC;QACnE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAClB,OAAO,MAAM,CAAC;IAClB,CAAC;IAED,MAAM,CAAC,IAAU;QACb,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAI5C,IAAI,CAAC,UAAU,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC;QACjC,IAAI,CAAC,KAAK,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC;QACvB,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveResultInfo.d.ts

@@ -1,7 +1,5 @@
 import { DataforseoLabsGoogleSearchIntentLiveItem } from "./DataforseoLabsGoogleSearchIntentLiveItem";
 export interface IDataforseoLabsGoogleSearchIntentLiveResultInfo {
-    /** *language code in a POST array* if there is no data, then the value is_`null`n */
-    language_code?: string | undefined;
     /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
     /** *array of items with relevant traffic estimation data* */
@@ -9,8 +7,6 @@ export interface IDataforseoLabsGoogleSearchIntentLiveResultInfo {
     [key: string]: any;
 }
 export declare class DataforseoLabsGoogleSearchIntentLiveResultInfo implements IDataforseoLabsGoogleSearchIntentLiveResultInfo {
-    /** *language code in a POST array* if there is no data, then the value is_`null`n */
-    language_code?: string | undefined;
     /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
     /** *array of items with relevant traffic estimation data* */

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveResultInfo.js

@@ -14,7 +14,6 @@ export class DataforseoLabsGoogleSearchIntentLiveResultInfo {
                 if (data.hasOwnProperty(property))
                     this[property] = data[property];
             }
-            this.language_code = data["language_code"];
             this.items_count = data["items_count"];
             if (Array.isArray(data["items"])) {
                 this.items = [];
@@ -32,7 +31,6 @@ export class DataforseoLabsGoogleSearchIntentLiveResultInfo {
     }
     toJSON(data) {
         data = typeof data === 'object' ? data : {};
-        data["language_code"] = this.language_code;
         data["items_count"] = this.items_count;
         data["items"] = null;
         if (Array.isArray(this.items)) {

package/dist/esm/models/DataforseoLabsGoogleSearchIntentLiveResultInfo.js.map

@@ -1 +1 @@
-{"version":3,"file":"DataforseoLabsGoogleSearchIntentLiveResultInfo.js","sourceRoot":"","sources":["../../../src/models/DataforseoLabsGoogleSearchIntentLiveResultInfo.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wCAAwC,EAA6C,MAAM,4CAA4C,CAAC;AAkBjJ,MAAM,OAAO,8CAA8C;IAoBvD,YAAY,IAAsD;QAElE,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBACvB,IAAK,CAAC,QAAQ,CAAC,GAAS,IAAK,CAAC,QAAQ,CAAC,CAAC;YACtD,CAAC;QACL,CAAC;IAED,CAAC;IAED,IAAI,CAAC,IAAU;QACX,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBAC7B,IAAI,CAAC,QAAQ,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC,CAAC;YACxC,CAAC;YACD,IAAI,CAAC,aAAa,GAAG,IAAI,CAAC,eAAe,CAAC,CAAC;YAC3C,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC,aAAa,CAAC,CAAC;YACvC,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,EAAE,CAAC;gBAC/B,IAAI,CAAC,KAAK,GAAG,EAAE,CAAC;gBAChB,KAAK,IAAI,IAAI,IAAI,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;oBAC7B,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,wCAAwC,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC;gBAC3E,CAAC;YACL,CAAC;QACL,CAAC;IACL,CAAC;IAED,MAAM,CAAC,MAAM,CAAC,IAAS;QACnB,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAG5C,IAAI,MAAM,GAAG,IAAI,8CAA8C,EAAE,CAAC;QAClE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAClB,OAAO,MAAM,CAAC;IAClB,CAAC;IAED,MAAM,CAAC,IAAU;QACb,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAI5C,IAAI,CAAC,eAAe,CAAC,GAAG,IAAI,CAAC,aAAa,CAAC;QAC3C,IAAI,CAAC,aAAa,CAAC,GAAG,IAAI,CAAC,WAAW,CAAC;QACvC,IAAI,CAAC,OAAO,CAAC,GAAG,IAAI,CAAC;QACrB,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC;YAC5B,IAAI,CAAC,OAAO,CAAC,GAAG,EAAE,CAAC;YACnB,KAAK,IAAI,IAAI,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;gBAC1B,IAAI,IAAI,IAAI,OAAO,IAAI,CAAC,MAAM,KAAK,UAAU,EAAE,CAAC;oBAC5C,IAAI,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC,IAAI,aAAJ,IAAI,uBAAJ,IAAI,CAAE,MAAM,EAAE,CAAC,CAAC;gBACvC,CAAC;YACL,CAAC;QACL,CAAC;QACD,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}
+{"version":3,"file":"DataforseoLabsGoogleSearchIntentLiveResultInfo.js","sourceRoot":"","sources":["../../../src/models/DataforseoLabsGoogleSearchIntentLiveResultInfo.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wCAAwC,EAA6C,MAAM,4CAA4C,CAAC;AAejJ,MAAM,OAAO,8CAA8C;IAevD,YAAY,IAAsD;QAElE,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBACvB,IAAK,CAAC,QAAQ,CAAC,GAAS,IAAK,CAAC,QAAQ,CAAC,CAAC;YACtD,CAAC;QACL,CAAC;IAED,CAAC;IAED,IAAI,CAAC,IAAU;QACX,IAAI,IAAI,EAAE,CAAC;YACP,KAAK,IAAI,QAAQ,IAAI,IAAI,EAAE,CAAC;gBACxB,IAAI,IAAI,CAAC,cAAc,CAAC,QAAQ,CAAC;oBAC7B,IAAI,CAAC,QAAQ,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC,CAAC;YACxC,CAAC;YACD,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC,aAAa,CAAC,CAAC;YACvC,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,EAAE,CAAC;gBAC/B,IAAI,CAAC,KAAK,GAAG,EAAE,CAAC;gBAChB,KAAK,IAAI,IAAI,IAAI,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;oBAC7B,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,wCAAwC,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC;gBAC3E,CAAC;YACL,CAAC;QACL,CAAC;IACL,CAAC;IAED,MAAM,CAAC,MAAM,CAAC,IAAS;QACnB,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAG5C,IAAI,MAAM,GAAG,IAAI,8CAA8C,EAAE,CAAC;QAClE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAClB,OAAO,MAAM,CAAC;IAClB,CAAC;IAED,MAAM,CAAC,IAAU;QACb,IAAI,GAAG,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC;QAI5C,IAAI,CAAC,aAAa,CAAC,GAAG,IAAI,CAAC,WAAW,CAAC;QACvC,IAAI,CAAC,OAAO,CAAC,GAAG,IAAI,CAAC;QACrB,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC;YAC5B,IAAI,CAAC,OAAO,CAAC,GAAG,EAAE,CAAC;YACnB,KAAK,IAAI,IAAI,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;gBAC1B,IAAI,IAAI,IAAI,OAAO,IAAI,CAAC,MAAM,KAAK,UAAU,EAAE,CAAC;oBAC5C,IAAI,CAAC,OAAO,CAAC,CAAC,IAAI,CAAC,IAAI,aAAJ,IAAI,uBAAJ,IAAI,CAAE,MAAM,EAAE,CAAC,CAAC;gBACvC,CAAC;YACL,CAAC;QACL,CAAC;QACD,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}

package/dist/esm/models/KeywordsDataGoogleTrendsExploreLiveRequestInfo.d.ts

@@ -1,5 +1,5 @@
 export interface IKeywordsDataGoogleTrendsExploreLiveRequestInfo {
-    /** *keywords* **required field** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
+    /** *keywords* **required field if you don't specify `category_code`** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
     /** *full name of search engine location* optional field if you don't use this field, you will recieve global results **if you use this field, you don't need to specify `location_code`** you can use this field as an array to set several locations, each corresponding to a specific keyword - [learn more](https://dataforseo.com/help-center/multiple-locations-in-google-trends-api); you can receive the list of available locations of the search engine with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `United Kingdom` */
     location_name?: string | undefined;
@@ -11,7 +11,7 @@ export interface IKeywordsDataGoogleTrendsExploreLiveRequestInfo {
     language_code?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** *google trends search category* optional field if you don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
+    /** *google trends search category* **required field if you don't specify `keywords`** if you don't specify `keywords`, the value of this field must be greater than `0` if you specify `keywords` and don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
     category_code?: number | undefined;
     /** *starting date of the time range* optional field if you don't specify this field, the current day and month of the preceding year will be used by default minimal value for the `web` type: `2004-01-01` minimal value for other types: `2008-01-01` date format: `'yyyy-mm-dd'` example: `'2019-01-15'` */
     date_from?: string | undefined;
@@ -26,7 +26,7 @@ export interface IKeywordsDataGoogleTrendsExploreLiveRequestInfo {
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreLiveRequestInfo implements IKeywordsDataGoogleTrendsExploreLiveRequestInfo {
-    /** *keywords* **required field** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
+    /** *keywords* **required field if you don't specify `category_code`** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
     /** *full name of search engine location* optional field if you don't use this field, you will recieve global results **if you use this field, you don't need to specify `location_code`** you can use this field as an array to set several locations, each corresponding to a specific keyword - [learn more](https://dataforseo.com/help-center/multiple-locations-in-google-trends-api); you can receive the list of available locations of the search engine with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `United Kingdom` */
     location_name?: string | undefined;
@@ -38,7 +38,7 @@ export declare class KeywordsDataGoogleTrendsExploreLiveRequestInfo implements I
     language_code?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** *google trends search category* optional field if you don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
+    /** *google trends search category* **required field if you don't specify `keywords`** if you don't specify `keywords`, the value of this field must be greater than `0` if you specify `keywords` and don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
     category_code?: number | undefined;
     /** *starting date of the time range* optional field if you don't specify this field, the current day and month of the preceding year will be used by default minimal value for the `web` type: `2004-01-01` minimal value for other types: `2008-01-01` date format: `'yyyy-mm-dd'` example: `'2019-01-15'` */
     date_from?: string | undefined;

package/dist/esm/models/KeywordsDataGoogleTrendsExploreTaskPostRequestInfo.d.ts

@@ -1,5 +1,5 @@
 export interface IKeywordsDataGoogleTrendsExploreTaskPostRequestInfo {
-    /** *keywords* **required field** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
+    /** *keywords* **required field if you don't specify `category_code`** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
     /** *full name of search engine location* optional field if you don't use this field, you will recieve global results **if you use this field, you don't need to specify `location_code`** you can use this field as an array to set several locations, each corresponding to a specific keyword - [learn more](https://dataforseo.com/help-center/multiple-locations-in-google-trends-api); you can receive the list of available locations of the search engine with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `United Kingdom` */
     location_name?: string | undefined;
@@ -11,7 +11,7 @@ export interface IKeywordsDataGoogleTrendsExploreTaskPostRequestInfo {
     language_code?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** *google trends search category* optional field if you don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
+    /** *google trends search category* **required field if you don't specify `keywords`** if you don't specify `keywords`, the value of this field must be greater than `0` if you specify `keywords` and don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
     category_code?: number | undefined;
     /** *starting date of the time range* optional field if you don't specify this field, the current day and month of the preceding year will be used by default minimal value for the `web` type: `2004-01-01` minimal value for other types: `2008-01-01` date format: `'yyyy-mm-dd'` example: `'2019-01-15'` */
     date_from?: string | undefined;
@@ -30,7 +30,7 @@ export interface IKeywordsDataGoogleTrendsExploreTaskPostRequestInfo {
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreTaskPostRequestInfo implements IKeywordsDataGoogleTrendsExploreTaskPostRequestInfo {
-    /** *keywords* **required field** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
+    /** *keywords* **required field if you don't specify `category_code`** the maximum number of keywords you can specify: 5 the maximum number of characters you can specify in a keyword: 100 the minimum number of characters must be greater than 1 comma characters (`,`) in the specified keywords will be unset and ignored **Note:** keywords cannot consist of a combination of the following characters: `|  ' - + = ~ ! : * ( ) [ ] { }` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis) */
     keywords?: string[] | undefined;
     /** *full name of search engine location* optional field if you don't use this field, you will recieve global results **if you use this field, you don't need to specify `location_code`** you can use this field as an array to set several locations, each corresponding to a specific keyword - [learn more](https://dataforseo.com/help-center/multiple-locations-in-google-trends-api); you can receive the list of available locations of the search engine with their `location_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `United Kingdom` */
     location_name?: string | undefined;
@@ -42,7 +42,7 @@ export declare class KeywordsDataGoogleTrendsExploreTaskPostRequestInfo implemen
     language_code?: string | undefined;
     /** type of element */
     type?: string | undefined;
-    /** *google trends search category* optional field if you don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
+    /** *google trends search category* **required field if you don't specify `keywords`** if you don't specify `keywords`, the value of this field must be greater than `0` if you specify `keywords` and don't specify this field, the `0` value will be applied by default and the search will be carried out across all available categories you can receive the list of available categories with their `category_code` by making a separate request to the `https://api.dataforseo.com/v3/keywords_data/google_trends/categories` */
     category_code?: number | undefined;
     /** *starting date of the time range* optional field if you don't specify this field, the current day and month of the preceding year will be used by default minimal value for the `web` type: `2004-01-01` minimal value for other types: `2008-01-01` date format: `'yyyy-mm-dd'` example: `'2019-01-15'` */
     date_from?: string | undefined;

package/dist/esm/models/OnPageInstantPagesResultInfo.d.ts

@@ -1,4 +1,4 @@
-import { BaseOnPageResourceItem } from "./BaseOnPageResourceItem";
+import { OnPageHtmlResourceItem } from "./BaseOnPageResourceItem";
 export interface IOnPageInstantPagesResultInfo {
     /** status of the crawling sessionpossible values: in_progress, finished */
     crawl_progress?: string | undefined;
@@ -9,7 +9,7 @@ export interface IOnPageInstantPagesResultInfo {
     /** number of items in the results array */
     items_count?: number | undefined;
     /** items array */
-    items?: BaseOnPageResourceItem[] | undefined;
+    items?: OnPageHtmlResourceItem[] | undefined;
     [key: string]: any;
 }
 export declare class OnPageInstantPagesResultInfo implements IOnPageInstantPagesResultInfo {
@@ -22,7 +22,7 @@ export declare class OnPageInstantPagesResultInfo implements IOnPageInstantPages
     /** number of items in the results array */
     items_count?: number | undefined;
     /** items array */
-    items?: BaseOnPageResourceItem[] | undefined;
+    items?: OnPageHtmlResourceItem[] | undefined;
     [key: string]: any;
     constructor(data?: IOnPageInstantPagesResultInfo);
     init(data?: any): void;

package/dist/esm/models/OnPageInstantPagesResultInfo.js

@@ -1,4 +1,4 @@
-import { BaseOnPageResourceItem } from "./BaseOnPageResourceItem.js";
+import { OnPageHtmlResourceItem } from "./BaseOnPageResourceItem.js";
 export class OnPageInstantPagesResultInfo {
     constructor(data) {
         if (data) {
@@ -21,7 +21,7 @@ export class OnPageInstantPagesResultInfo {
             if (Array.isArray(data["items"])) {
                 this.items = [];
                 for (let item of data["items"]) {
-                    this.items.push(BaseOnPageResourceItem.fromJS(item));
+                    this.items.push(OnPageHtmlResourceItem.fromJS(item));
                 }
             }
         }

package/dist/esm/models/SerpGoogleLocalFinderLiveAdvancedRequestInfo.d.ts

@@ -5,7 +5,7 @@ export interface ISerpGoogleLocalFinderLiveAdvancedRequestInfo {
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `100` default value for `mobile`: `10` max value for `mobile`: `100` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively;; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `100` **Your account will be billed per each SERP containing up to 10 results;** Setting depth above 10 may result in additional charges if the search engine returns more than 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *device type* optional field return results for a specific device type can take the values:`desktop`, `mobile` default value: `desktop` */
     device?: string | undefined;
@@ -34,7 +34,7 @@ export declare class SerpGoogleLocalFinderLiveAdvancedRequestInfo implements ISe
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `100` default value for `mobile`: `10` max value for `mobile`: `100` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively;; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `100` **Your account will be billed per each SERP containing up to 10 results;** Setting depth above 10 may result in additional charges if the search engine returns more than 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *device type* optional field return results for a specific device type can take the values:`desktop`, `mobile` default value: `desktop` */
     device?: string | undefined;

package/dist/esm/models/SerpGoogleLocalFinderLiveHtmlRequestInfo.d.ts

@@ -5,7 +5,7 @@ export interface ISerpGoogleLocalFinderLiveHtmlRequestInfo {
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `100` default value for `mobile`: `10` max value for `mobile`: `100` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `100` **Your account will be billed per each SERP containing up to 10 results;** Setting depth above 10 may result in additional charges if the search engine returns more than 10 results; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *device type* optional field return results for a specific device type can take the values:`desktop`, `mobile` default value: `desktop` */
     device?: string | undefined;
@@ -32,7 +32,7 @@ export declare class SerpGoogleLocalFinderLiveHtmlRequestInfo implements ISerpGo
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `100` default value for `mobile`: `10` max value for `mobile`: `100` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `100` **Your account will be billed per each SERP containing up to 10 results;** Setting depth above 10 may result in additional charges if the search engine returns more than 10 results; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *device type* optional field return results for a specific device type can take the values:`desktop`, `mobile` default value: `desktop` */
     device?: string | undefined;

package/dist/esm/models/SerpGoogleLocalFinderTaskPostRequestInfo.d.ts

@@ -5,7 +5,7 @@ export interface ISerpGoogleLocalFinderTaskPostRequestInfo {
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `500` default value for `mobile`: `10` max value for `mobile`: `350` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `350` **your account will be billed per each SERP containing up to 10 results;** setting depth above 10 may result in additional charges if the search engine returns more than 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *task priority* optional field can take the following values: 1 – normal execution priority (set by default) 2 – high execution priority You will be additionally charged for the tasks with high execution priority. The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     priority?: number | undefined;
@@ -40,7 +40,7 @@ export declare class SerpGoogleLocalFinderTaskPostRequestInfo implements ISerpGo
     location_code?: number | undefined;
     /** *search engine language code* **required field if you don't specify** `language_name` **if you use this field, you don't need to specify `language_name`** you can receive the list of available languages of the search engine with their `language_code` by making a separate request to the `https://api.dataforseo.com/v3/serp/{{low_se_name}}/languages` example:`en` */
     language_code?: string | undefined;
-    /** *parsing depth* optional field number of results in SERP default value for `desktop`: `20` max value for `desktop`: `500` default value for `mobile`: `10` max value for `mobile`: `350` **Your account will be billed per each SERP containing up to 20 results for desktop or up to 10 results for a mobile device;** Setting depth above 20 for desktop or above 10 for mobile may result in additional charges if the search engine returns more than 20 or 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
+    /** *parsing depth* optional field number of results in SERP default value: `10` max value: `350` **your account will be billed per each SERP containing up to 10 results;** setting depth above 10 may result in additional charges if the search engine returns more than 10 results respectively; If the specified depth is higher than the number of results in the response, the difference will be refunded to your account balance automatically The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     depth?: number | undefined;
     /** *task priority* optional field can take the following values: 1 – normal execution priority (set by default) 2 – high execution priority You will be additionally charged for the tasks with high execution priority. The cost can be calculated on the [Pricing](https://dataforseo.com/pricing/serp/google-local-finder-serp-api) page. */
     priority?: number | undefined;