dataforseo-client 2.1.2 → 2.1.3

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

@@ -1,30 +1,30 @@
 export interface IKeywordsDataDataforseoTrendsLocationsCountryResultInfo {
-    /** location code */
+    /** *location code* */
     location_code?: number | undefined;
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** the code of the superordinate location example: 'location_code': 9041134, 'location_name': 'Vienna International Airport,Lower Austria,Austria', 'location_code_parent': 20044 where location_code_parent corresponds to: 'location_code': 20044, 'location_name': 'Lower Austria,Austria' */
+    /** *the code of the superordinate location* example: `'location_code': 9041134,'location_name': 'Vienna International Airport,Lower Austria,Austria','location_code_parent': 20044` where `location_code_parent` corresponds to: `'location_code': 20044,'location_name': 'Lower Austria,Austria'` */
     location_code_parent?: number | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
-    /** location type possible values according to Google’s target types */
+    /** *location type* possible values according to [Google’s target types](https://developers.google.com/adwords/api/docs/appendix/geotargeting) */
     location_type?: string | undefined;
-    /** DataForSEO trends location identifier you can use this field for matching obtained results with the location_code parameter specified in the request */
+    /** *DataForSEO trends location identifier* you can use this field for matching obtained results with the `location_code` parameter specified in the request */
     geo_id?: string | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataDataforseoTrendsLocationsCountryResultInfo implements IKeywordsDataDataforseoTrendsLocationsCountryResultInfo {
-    /** location code */
+    /** *location code* */
     location_code?: number | undefined;
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** the code of the superordinate location example: 'location_code': 9041134, 'location_name': 'Vienna International Airport,Lower Austria,Austria', 'location_code_parent': 20044 where location_code_parent corresponds to: 'location_code': 20044, 'location_name': 'Lower Austria,Austria' */
+    /** *the code of the superordinate location* example: `'location_code': 9041134,'location_name': 'Vienna International Airport,Lower Austria,Austria','location_code_parent': 20044` where `location_code_parent` corresponds to: `'location_code': 20044,'location_name': 'Lower Austria,Austria'` */
     location_code_parent?: number | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
-    /** location type possible values according to Google’s target types */
+    /** *location type* possible values according to [Google’s target types](https://developers.google.com/adwords/api/docs/appendix/geotargeting) */
     location_type?: string | undefined;
-    /** DataForSEO trends location identifier you can use this field for matching obtained results with the location_code parameter specified in the request */
+    /** *DataForSEO trends location identifier* you can use this field for matching obtained results with the `location_code` parameter specified in the request */
     geo_id?: string | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataDataforseoTrendsLocationsCountryResultInfo);

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

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

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

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

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

@@ -1,30 +1,30 @@
 export interface IKeywordsDataDataforseoTrendsLocationsResultInfo {
-    /** location code */
+    /** *location code* */
     location_code?: number | undefined;
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** the code of the superordinate location example: 'location_code': 9041134, 'location_name': 'Vienna International Airport,Lower Austria,Austria', 'location_code_parent': 20044 where location_code_parent corresponds to: 'location_code': 20044, 'location_name': 'Lower Austria,Austria' */
+    /** *the code of the superordinate location* example: `'location_code': 9041134,'location_name': 'Vienna International Airport,Lower Austria,Austria','location_code_parent': 20044` where `location_code_parent` corresponds to: `'location_code': 20044,'location_name': 'Lower Austria,Austria'` */
     location_code_parent?: number | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
-    /** location type possible values according to Google’s target types */
+    /** *location type* possible values according to [Google’s target types](https://developers.google.com/adwords/api/docs/appendix/geotargeting) */
     location_type?: string | undefined;
-    /** DataForSEO trends location identifier you can use this field for matching obtained results with the location_code parameter specified in the request */
+    /** *DataForSEO trends location identifier* you can use this field for matching obtained results with the `location_code` parameter specified in the request */
     geo_id?: string | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataDataforseoTrendsLocationsResultInfo implements IKeywordsDataDataforseoTrendsLocationsResultInfo {
-    /** location code */
+    /** *location code* */
     location_code?: number | undefined;
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** the code of the superordinate location example: 'location_code': 9041134, 'location_name': 'Vienna International Airport,Lower Austria,Austria', 'location_code_parent': 20044 where location_code_parent corresponds to: 'location_code': 20044, 'location_name': 'Lower Austria,Austria' */
+    /** *the code of the superordinate location* example: `'location_code': 9041134,'location_name': 'Vienna International Airport,Lower Austria,Austria','location_code_parent': 20044` where `location_code_parent` corresponds to: `'location_code': 20044,'location_name': 'Lower Austria,Austria'` */
     location_code_parent?: number | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
-    /** location type possible values according to Google’s target types */
+    /** *location type* possible values according to [Google’s target types](https://developers.google.com/adwords/api/docs/appendix/geotargeting) */
     location_type?: string | undefined;
-    /** DataForSEO trends location identifier you can use this field for matching obtained results with the location_code parameter specified in the request */
+    /** *DataForSEO trends location identifier* you can use this field for matching obtained results with the `location_code` parameter specified in the request */
     geo_id?: string | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataDataforseoTrendsLocationsResultInfo);

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

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

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

@@ -1,38 +1,38 @@
 export interface IKeywordsDataDataforseoTrendsMergedDataLiveRequestInfo {
-    /** keywords required field the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *keywords* **required field** the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used 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 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/dataforseo_trends/locations note that the data will be provided for the country the specified location_name belongs to; example: United Kingdom */
+    /** *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 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/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_name` belongs to;** example: `United Kingdom` */
     location_name?: string | undefined;
-    /** search engine location code 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_name you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_code belongs to; example: 2840 */
+    /** *search engine location code* 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_name`** you can receive the list of available locations of the search engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_code` belongs to;** example: `2840` */
     location_code?: number | undefined;
     /** type of element */
     type?: string | 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' */
+    /** *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;
-    /** 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: '2019-01-15' */
+    /** *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: `'2019-01-15'` */
     date_to?: string | undefined;
-    /** preset time ranges optional field if you specify date_from or date_to parameters, this field will be ignored when setting a task possible values for all type parameters: past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years */
+    /** *preset time ranges* optional field if you specify `date_from` or `date_to` parameters, this field will be ignored when setting a task *possible values for all `type` parameters:* `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` */
     time_range?: 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 KeywordsDataDataforseoTrendsMergedDataLiveRequestInfo implements IKeywordsDataDataforseoTrendsMergedDataLiveRequestInfo {
-    /** keywords required field the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *keywords* **required field** the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used 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 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/dataforseo_trends/locations note that the data will be provided for the country the specified location_name belongs to; example: United Kingdom */
+    /** *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 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/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_name` belongs to;** example: `United Kingdom` */
     location_name?: string | undefined;
-    /** search engine location code 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_name you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_code belongs to; example: 2840 */
+    /** *search engine location code* 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_name`** you can receive the list of available locations of the search engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_code` belongs to;** example: `2840` */
     location_code?: number | undefined;
     /** type of element */
     type?: string | 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' */
+    /** *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;
-    /** 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: '2019-01-15' */
+    /** *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: `'2019-01-15'` */
     date_to?: string | undefined;
-    /** preset time ranges optional field if you specify date_from or date_to parameters, this field will be ignored when setting a task possible values for all type parameters: past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years */
+    /** *preset time ranges* optional field if you specify `date_from` or `date_to` parameters, this field will be ignored when setting a task *possible values for all `type` parameters:* `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` */
     time_range?: 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?: IKeywordsDataDataforseoTrendsMergedDataLiveRequestInfo);

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

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

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

@@ -1,35 +1,35 @@
 import { BaseKeywordDataDataforseoTrendsItem } from "./BaseKeywordDataDataforseoTrendsItem";
 export interface IKeywordsDataDataforseoTrendsMergedDataLiveResultInfo {
-    /** keywords in a POST array */
+    /** *keywords in a POST array* */
     keywords?: string[] | undefined;
     /** type of element */
     type?: string | undefined;
-    /** location code in a POST array if there is no data, then the value is null */
+    /** *location code in a POST array* if there is no data, then the value is_`null`n */
     location_code?: number | undefined;
-    /** language code in a POST array if there is no data, then the value is null */
+    /** *language code in a POST array* if there is no data, then the value is_`null`n */
     language_code?: 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;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** contains keyword popularity and related data */
+    /** *contains keyword popularity and related data* */
     items?: BaseKeywordDataDataforseoTrendsItem[] | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataDataforseoTrendsMergedDataLiveResultInfo implements IKeywordsDataDataforseoTrendsMergedDataLiveResultInfo {
-    /** keywords in a POST array */
+    /** *keywords in a POST array* */
     keywords?: string[] | undefined;
     /** type of element */
     type?: string | undefined;
-    /** location code in a POST array if there is no data, then the value is null */
+    /** *location code in a POST array* if there is no data, then the value is_`null`n */
     location_code?: number | undefined;
-    /** language code in a POST array if there is no data, then the value is null */
+    /** *language code in a POST array* if there is no data, then the value is_`null`n */
     language_code?: 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;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** contains keyword popularity and related data */
+    /** *contains keyword popularity and related data* */
     items?: BaseKeywordDataDataforseoTrendsItem[] | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataDataforseoTrendsMergedDataLiveResultInfo);

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

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

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

@@ -1,38 +1,38 @@
 export interface IKeywordsDataDataforseoTrendsSubregionInterestsLiveRequestInfo {
-    /** keywords required field the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *keywords* **required field** the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used 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 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/dataforseo_trends/locations note that the data will be provided for the country the specified location_name belongs to; example: United Kingdom */
+    /** *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 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/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_name` belongs to;** example: `United Kingdom` */
     location_name?: string | undefined;
-    /** search engine location code 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_name you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_code belongs to; example: 2840 */
+    /** *search engine location code* 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_name`** you can receive the list of available locations of the search engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_code` belongs to;** example: `2840` */
     location_code?: number | undefined;
     /** type of element */
     type?: string | 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' */
+    /** *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;
-    /** 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: '2019-01-15' */
+    /** *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: `'2019-01-15'` */
     date_to?: string | undefined;
-    /** preset time ranges optional field if you specify date_from or date_to parameters, this field will be ignored when setting a task possible values for all type parameters: past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years */
+    /** *preset time ranges* optional field if you specify `date_from` or `date_to` parameters, this field will be ignored when setting a task *possible values for all `type` parameters:* `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` */
     time_range?: 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 KeywordsDataDataforseoTrendsSubregionInterestsLiveRequestInfo implements IKeywordsDataDataforseoTrendsSubregionInterestsLiveRequestInfo {
-    /** keywords required field the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *keywords* **required field** the maximum number of keywords you can specify: 5 avoid symbols and special characters (e.g., UTF symbols, emojis); specifying non-Latin characters, you’ll get data for the countries where they are used 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 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/dataforseo_trends/locations note that the data will be provided for the country the specified location_name belongs to; example: United Kingdom */
+    /** *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 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/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_name` belongs to;** example: `United Kingdom` */
     location_name?: string | undefined;
-    /** search engine location code 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_name you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations note that the data will be provided for the country the specified location_code belongs to; example: 2840 */
+    /** *search engine location code* 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_name`** you can receive the list of available locations of the search engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/dataforseo_trends/locations` **note that the data will be provided for the country the specified `location_code` belongs to;** example: `2840` */
     location_code?: number | undefined;
     /** type of element */
     type?: string | 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' */
+    /** *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;
-    /** 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: '2019-01-15' */
+    /** *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: `'2019-01-15'` */
     date_to?: string | undefined;
-    /** preset time ranges optional field if you specify date_from or date_to parameters, this field will be ignored when setting a task possible values for all type parameters: past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years */
+    /** *preset time ranges* optional field if you specify `date_from` or `date_to` parameters, this field will be ignored when setting a task *possible values for all `type` parameters:* `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` */
     time_range?: 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?: IKeywordsDataDataforseoTrendsSubregionInterestsLiveRequestInfo);

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

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

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

@@ -1,35 +1,35 @@
 import { DataforseoTrendsSubregionInterestsElementItem } from "./BaseKeywordDataDataforseoTrendsItem";
 export interface IKeywordsDataDataforseoTrendsSubregionInterestsLiveResultInfo {
-    /** keywords in a POST array */
+    /** *keywords in a POST array* */
     keywords?: string[] | undefined;
     /** type of element */
     type?: string | undefined;
-    /** location code in a POST array if there is no data, then the value is null */
+    /** *location code in a POST array* if there is no data, then the value is_`null`n */
     location_code?: number | undefined;
-    /** language code in a POST array if there is no data, then the value is null */
+    /** *language code in a POST array* if there is no data, then the value is_`null`n */
     language_code?: 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;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** contains keyword popularity and related data */
+    /** *contains keyword popularity and related data* */
     items?: DataforseoTrendsSubregionInterestsElementItem[] | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataDataforseoTrendsSubregionInterestsLiveResultInfo implements IKeywordsDataDataforseoTrendsSubregionInterestsLiveResultInfo {
-    /** keywords in a POST array */
+    /** *keywords in a POST array* */
     keywords?: string[] | undefined;
     /** type of element */
     type?: string | undefined;
-    /** location code in a POST array if there is no data, then the value is null */
+    /** *location code in a POST array* if there is no data, then the value is_`null`n */
     location_code?: number | undefined;
-    /** language code in a POST array if there is no data, then the value is null */
+    /** *language code in a POST array* if there is no data, then the value is_`null`n */
     language_code?: 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;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** contains keyword popularity and related data */
+    /** *contains keyword popularity and related data* */
     items?: DataforseoTrendsSubregionInterestsElementItem[] | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataDataforseoTrendsSubregionInterestsLiveResultInfo);

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

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

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

@@ -1,26 +1,26 @@
 export interface IKeywordsDataErrorsRequestInfo {
-    /** the maximum number of returned tasks that responded with an error optional field default value: 1000 maximum value: 1000 */
+    /** *the maximum number of returned tasks that responded with an error* optional field default value: `1000` maximum value: `1000` */
     limit?: number | undefined;
-    /** offset in the results array of returned tasks optional field default value: 0 if you specify the 10 value, the first ten tasks in the results array will be omitted and the data will be provided for the successive tasks */
+    /** *offset in the results array of returned tasks* optional field default value: `0` if you specify the `10` value, the first ten tasks in the results array will be omitted and the data will be provided for the successive tasks */
     offset?: number | undefined;
-    /** return tasks with a certain function use this field to obtain a list of tasks that returned an error filtered by a certain function you can filter the results by the values you receive in the function fields of the API response i.e., once you receive unfiltered results, you can call this API again to filter them by function example: keywords_data/keywords_for_site/task_post, postback_url, pingback_url */
+    /** *return tasks with a certain function* use this field to obtain a list of tasks that returned an error filtered by a certain function you can filter the results by the values you receive in the `function` fields of the API response i.e., once you receive unfiltered results, you can call this API again to filter them by `function`  example: `keywords_data/keywords_for_site/task_post`, `postback_url`, `pingback_url` */
     filtered_function?: string | undefined;
-    /** start time for filtering results optional field allows filtering results by the datetime parameter within the range of the last 7 days; must be specified in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2021-11-15 12:57:46 +00:00 */
+    /** *start time for filtering results* optional field allows filtering results by the `datetime` parameter within the range of the last 7 days; must be specified in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2021-11-15 12:57:46 +00:00` */
     datetime_from?: string | undefined;
-    /** finish time for filtering results optional field allows filtering results by the datetime parameter within the range of the last 7 days; must be specified in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2021-11-15 13:57:46 +00:00 */
+    /** *finish time for filtering results* optional field allows filtering results by the `datetime` parameter within the range of the last 7 days; must be specified in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2021-11-15 13:57:46 +00:00` */
     datetime_to?: string | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataErrorsRequestInfo implements IKeywordsDataErrorsRequestInfo {
-    /** the maximum number of returned tasks that responded with an error optional field default value: 1000 maximum value: 1000 */
+    /** *the maximum number of returned tasks that responded with an error* optional field default value: `1000` maximum value: `1000` */
     limit?: number | undefined;
-    /** offset in the results array of returned tasks optional field default value: 0 if you specify the 10 value, the first ten tasks in the results array will be omitted and the data will be provided for the successive tasks */
+    /** *offset in the results array of returned tasks* optional field default value: `0` if you specify the `10` value, the first ten tasks in the results array will be omitted and the data will be provided for the successive tasks */
     offset?: number | undefined;
-    /** return tasks with a certain function use this field to obtain a list of tasks that returned an error filtered by a certain function you can filter the results by the values you receive in the function fields of the API response i.e., once you receive unfiltered results, you can call this API again to filter them by function example: keywords_data/keywords_for_site/task_post, postback_url, pingback_url */
+    /** *return tasks with a certain function* use this field to obtain a list of tasks that returned an error filtered by a certain function you can filter the results by the values you receive in the `function` fields of the API response i.e., once you receive unfiltered results, you can call this API again to filter them by `function`  example: `keywords_data/keywords_for_site/task_post`, `postback_url`, `pingback_url` */
     filtered_function?: string | undefined;
-    /** start time for filtering results optional field allows filtering results by the datetime parameter within the range of the last 7 days; must be specified in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2021-11-15 12:57:46 +00:00 */
+    /** *start time for filtering results* optional field allows filtering results by the `datetime` parameter within the range of the last 7 days; must be specified in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2021-11-15 12:57:46 +00:00` */
     datetime_from?: string | undefined;
-    /** finish time for filtering results optional field allows filtering results by the datetime parameter within the range of the last 7 days; must be specified in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2021-11-15 13:57:46 +00:00 */
+    /** *finish time for filtering results* optional field allows filtering results by the `datetime` parameter within the range of the last 7 days; must be specified in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2021-11-15 13:57:46 +00:00` */
     datetime_to?: string | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataErrorsRequestInfo);

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

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

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

@@ -1,46 +1,46 @@
 export interface IKeywordsDataErrorsResultInfo {
-    /** task identifier unique task identifier in our system in the UUID format */
+    /** *task identifier* **unique task identifier in our system in the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) format** */
     id?: string | undefined;
-    /** date and time when an error occurred 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 an error occurred* in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** corresponding API function */
+    /** *corresponding API function* */
     function?: string | undefined;
-    /** error code */
+    /** *error code* */
     error_code?: number | undefined;
-    /** error message or error URL error message (see full list) or URL that caused an error */
+    /** *error message or error URL* error message [(see full list)](https://docs.dataforseo.com/v3/appendix/errors/) or URL that caused an error */
     error_message?: string | undefined;
-    /** URL that caused an error URL you used for making an API call or pingback/postback URL */
+    /** *URL that caused an error* URL you used for making an API call or pingback/postback URL */
     http_url?: string | undefined;
-    /** HTTP method */
+    /** *HTTP method* */
     http_method?: string | undefined;
-    /** HTTP status code */
+    /** *HTTP status code* */
     http_code?: number | undefined;
-    /** time taken by HTTP request for tasks set with a pingback/postback, this field will show the time it took your server to respond */
+    /** *time taken by HTTP request* for tasks set with a pingback/postback, this field will show the time it took your server to respond */
     http_time?: number | undefined;
-    /** HTTP response server response */
+    /** *HTTP response* server response */
     http_response?: string | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataErrorsResultInfo implements IKeywordsDataErrorsResultInfo {
-    /** task identifier unique task identifier in our system in the UUID format */
+    /** *task identifier* **unique task identifier in our system in the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) format** */
     id?: string | undefined;
-    /** date and time when an error occurred 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 an error occurred* in the UTC format: 'yyyy-mm-dd hh-mm-ss +00:00' example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** corresponding API function */
+    /** *corresponding API function* */
     function?: string | undefined;
-    /** error code */
+    /** *error code* */
     error_code?: number | undefined;
-    /** error message or error URL error message (see full list) or URL that caused an error */
+    /** *error message or error URL* error message [(see full list)](https://docs.dataforseo.com/v3/appendix/errors/) or URL that caused an error */
     error_message?: string | undefined;
-    /** URL that caused an error URL you used for making an API call or pingback/postback URL */
+    /** *URL that caused an error* URL you used for making an API call or pingback/postback URL */
     http_url?: string | undefined;
-    /** HTTP method */
+    /** *HTTP method* */
     http_method?: string | undefined;
-    /** HTTP status code */
+    /** *HTTP status code* */
     http_code?: number | undefined;
-    /** time taken by HTTP request for tasks set with a pingback/postback, this field will show the time it took your server to respond */
+    /** *time taken by HTTP request* for tasks set with a pingback/postback, this field will show the time it took your server to respond */
     http_time?: number | undefined;
-    /** HTTP response server response */
+    /** *HTTP response* server response */
     http_response?: string | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataErrorsResultInfo);

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

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