dataforseo-client 2.1.2 → 2.1.3

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

@@ -1,18 +1,18 @@
 export interface IKeywordsDataGoogleTrendsCategoriesResultInfo {
-    /** unique google trends category identifier */
+    /** *unique google trends category identifier* */
     category_code?: number | undefined;
-    /** name of the google trends category */
+    /** *name of the google trends category* */
     category_name?: string | undefined;
-    /** the code of the superordinate category example: 'category_code': 1100, 'category_name': 'Superhero Films', 'category_code_parent': 1097 where category_code_parent corresponds to: 'category_code': 1097, 'category_name': 'Action & Adventure Films' */
+    /** *the code of the superordinate category* example: `'category_code': 1100,` `'category_name': 'Superhero Films',` `'category_code_parent': 1097`  where `category_code_parent` corresponds to:  `'category_code': 1097,` `'category_name': 'Action & Adventure Films'` */
     category_code_parent?: number | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsCategoriesResultInfo implements IKeywordsDataGoogleTrendsCategoriesResultInfo {
-    /** unique google trends category identifier */
+    /** *unique google trends category identifier* */
     category_code?: number | undefined;
-    /** name of the google trends category */
+    /** *name of the google trends category* */
     category_name?: string | undefined;
-    /** the code of the superordinate category example: 'category_code': 1100, 'category_name': 'Superhero Films', 'category_code_parent': 1097 where category_code_parent corresponds to: 'category_code': 1097, 'category_name': 'Action & Adventure Films' */
+    /** *the code of the superordinate category* example: `'category_code': 1100,` `'category_name': 'Superhero Films',` `'category_code_parent': 1097`  where `category_code_parent` corresponds to:  `'category_code': 1097,` `'category_name': 'Action & Adventure Films'` */
     category_code_parent?: number | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataGoogleTrendsCategoriesResultInfo);

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

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

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

@@ -1,54 +1,54 @@
 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 */
+    /** *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?: 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; 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 */
+    /** *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;
-    /** 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 use this field as an array to set several locations, each corresponding to a specific keyword – learn more; 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/google_trends/locations 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 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 engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `2840` */
     location_code?: string | undefined;
-    /** full name of search engine language optional field default value: English if you use this field, you don’t need to specify language_code you can receive the list of available languages of the search engine with their language_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: English */
+    /** *full name of search engine language* optional field default value: `English` if you use this field, you don't need to specify `language_code` you can receive the list of available languages of the search engine with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `English` */
     language_name?: string | undefined;
-    /** search engine language code optional field default value: en 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 https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: en */
+    /** *search engine language code* optional field default value: `en` 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 `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `en` */
     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* 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` */
     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' */
+    /** *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_hour, past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years possible values for web only: 2004_present possible values for news, youtube, images, froogle: 2008_present */
+    /** *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_hour`, `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` *possible values for `web` only:* `2004_present` *possible values for `news`, `youtube`, `images`, `froogle`:* `2008_present` */
     time_range?: string | undefined;
-    /** types of items returned optional field to speed up the execution of the request, specify one item at a time; possible values: 'google_trends_graph', 'google_trends_map', 'google_trends_topics_list','google_trends_queries_list' default value: 'google_trends_graph' Note: to obtain google_trends_topics_list and google_trends_queries_list items, specify no more than 1 keyword in the keywords field */
+    /** *types of items returned* optional field to speed up the execution of the request, specify one item at a time; possible values: `'google_trends_graph'`, `'google_trends_map'`, `'google_trends_topics_list'`,`'google_trends_queries_list'` default value: `'google_trends_graph'` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword in the `keywords` field */
     item_types?: 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 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 */
+    /** *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?: 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; 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 */
+    /** *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;
-    /** 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 use this field as an array to set several locations, each corresponding to a specific keyword – learn more; 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/google_trends/locations 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 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 engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `2840` */
     location_code?: string | undefined;
-    /** full name of search engine language optional field default value: English if you use this field, you don’t need to specify language_code you can receive the list of available languages of the search engine with their language_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: English */
+    /** *full name of search engine language* optional field default value: `English` if you use this field, you don't need to specify `language_code` you can receive the list of available languages of the search engine with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `English` */
     language_name?: string | undefined;
-    /** search engine language code optional field default value: en 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 https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: en */
+    /** *search engine language code* optional field default value: `en` 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 `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `en` */
     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* 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` */
     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' */
+    /** *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_hour, past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years possible values for web only: 2004_present possible values for news, youtube, images, froogle: 2008_present */
+    /** *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_hour`, `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` *possible values for `web` only:* `2004_present` *possible values for `news`, `youtube`, `images`, `froogle`:* `2008_present` */
     time_range?: string | undefined;
-    /** types of items returned optional field to speed up the execution of the request, specify one item at a time; possible values: 'google_trends_graph', 'google_trends_map', 'google_trends_topics_list','google_trends_queries_list' default value: 'google_trends_graph' Note: to obtain google_trends_topics_list and google_trends_queries_list items, specify no more than 1 keyword in the keywords field */
+    /** *types of items returned* optional field to speed up the execution of the request, specify one item at a time; possible values: `'google_trends_graph'`, `'google_trends_map'`, `'google_trends_topics_list'`,`'google_trends_queries_list'` default value: `'google_trends_graph'` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword in the `keywords` field */
     item_types?: 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?: IKeywordsDataGoogleTrendsExploreLiveRequestInfo);

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

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

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

@@ -1,39 +1,39 @@
 import { BaseKeywordDataGoogleTrendsItem } from "./BaseKeywordDataGoogleTrendsItem";
 export interface IKeywordsDataGoogleTrendsExploreLiveResultInfo {
-    /** 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;
-    /** direct URL to the Google Trends results you can use it to make sure that we provided accurate results */
+    /** *direct URL to the Google Trends results* you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** items on the Google Trends page */
+    /** *items on the Google Trends page* */
     items?: BaseKeywordDataGoogleTrendsItem[] | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreLiveResultInfo implements IKeywordsDataGoogleTrendsExploreLiveResultInfo {
-    /** 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;
-    /** direct URL to the Google Trends results you can use it to make sure that we provided accurate results */
+    /** *direct URL to the Google Trends results* you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** items on the Google Trends page */
+    /** *items on the Google Trends page* */
     items?: BaseKeywordDataGoogleTrendsItem[] | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataGoogleTrendsExploreLiveResultInfo);

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

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

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

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

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

@@ -1,39 +1,39 @@
 import { BaseKeywordDataGoogleTrendsItem } from "./BaseKeywordDataGoogleTrendsItem";
 export interface IKeywordsDataGoogleTrendsExploreTaskGetResultInfo {
-    /** 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;
-    /** direct URL to the Google Trends results you can use it to make sure that we provided accurate results */
+    /** *direct URL to the Google Trends results* you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** items on the Google Trends page */
+    /** *items on the Google Trends page* */
     items?: BaseKeywordDataGoogleTrendsItem[] | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreTaskGetResultInfo implements IKeywordsDataGoogleTrendsExploreTaskGetResultInfo {
-    /** 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;
-    /** direct URL to the Google Trends results you can use it to make sure that we provided accurate results */
+    /** *direct URL to the Google Trends results* you can use it to make sure that we provided accurate results */
     check_url?: string | undefined;
-    /** date and time when the result was received in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2019-11-15 12:57:46 +00:00 */
+    /** *date and time when the result was received* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2019-11-15 12:57:46 +00:00` */
     datetime?: string | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the **`items`** array* */
     items_count?: number | undefined;
-    /** items on the Google Trends page */
+    /** *items on the Google Trends page* */
     items?: BaseKeywordDataGoogleTrendsItem[] | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataGoogleTrendsExploreTaskGetResultInfo);

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

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

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

@@ -1,62 +1,62 @@
 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 */
+    /** *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?: 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; 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 */
+    /** *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;
-    /** 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 use this field as an array to set several locations, each corresponding to a specific keyword – learn more; 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/google_trends/locations 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 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 engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `2840` */
     location_code?: string | undefined;
-    /** full name of search engine language optional field default value: English if you use this field, you don’t need to specify language_code you can receive the list of available languages of the search engine with their language_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: English */
+    /** *full name of search engine language* optional field default value: `English` if you use this field, you don't need to specify `language_code` you can receive the list of available languages of the search engine with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `English` */
     language_name?: string | undefined;
-    /** search engine language code optional field default value: en 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 https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: en */
+    /** *search engine language code* optional field default value: `en` 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 `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `en` */
     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* 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` */
     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' */
+    /** *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_hour, past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years possible values for web only: 2004_present possible values for news, youtube, images, froogle: 2008_present */
+    /** *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_hour`, `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` *possible values for `web` only:* `2004_present` *possible values for `news`, `youtube`, `images`, `froogle`:* `2008_present` */
     time_range?: string | undefined;
-    /** types of items returned optional field to speed up the execution of the request, specify one item at a time; possible values: 'google_trends_graph', 'google_trends_map', 'google_trends_topics_list','google_trends_queries_list' default value: 'google_trends_graph' Note: to obtain google_trends_topics_list and google_trends_queries_list items, specify no more than 1 keyword in the keywords field */
+    /** *types of items returned* optional field to speed up the execution of the request, specify one item at a time; possible values: `'google_trends_graph'`, `'google_trends_map'`, `'google_trends_topics_list'`,`'google_trends_queries_list'` default value: `'google_trends_graph'` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword in the `keywords` field */
     item_types?: string[] | undefined;
-    /** URL for sending task results optional field once the task is completed, we will send a POST request with its results compressed in the gzip format to the postback_url you specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request. example: http://your-server.com/postbackscript?id=$id http://your-server.com/postbackscript?id=$id&tag=$tag Note: special characters in postback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center */
+    /** *URL for sending task results* optional field once the task is completed, we will send a POST request with its results compressed in the `gzip` format to the `postback_url` you specified you can use the ‘$id’ string as a `$id` variable and ‘$tag’ as urlencoded `$tag` variable. We will set the necessary values before sending the request. example: `http://your-server.com/postbackscript?id=$id` `http://your-server.com/postbackscript?id=$id&tag=$tag` **Note:** special characters in `postback_url` will be urlencoded; i.a., the `#` character will be encoded into `%23` learn more on our [Help Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api) */
     postback_url?: string | undefined;
-    /** notification URL of a completed task optional field when a task is completed we will notify you by GET request sent to the URL you have specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request example: http://your-server.com/pingscript?id=$id http://your-server.com/pingscript?id=$id&tag=$tag Note: special characters in pingback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center */
+    /** *notification URL of a completed task* optional field when a task is completed we will notify you by GET request sent to the URL you have specified you can use the ‘$id’ string as a `$id` variable and ‘$tag’ as urlencoded `$tag` variable. We will set the necessary values before sending the request example: `http://your-server.com/pingscript?id=$id` `http://your-server.com/pingscript?id=$id&tag=$tag` **Note:** special characters in `pingback_url` will be urlencoded; i.a., the `#` character will be encoded into `%23` learn more on our [Help Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api) */
     pingback_url?: 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 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 */
+    /** *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?: 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; 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 */
+    /** *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;
-    /** 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 use this field as an array to set several locations, each corresponding to a specific keyword – learn more; 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/google_trends/locations 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 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 engines with their `location_code` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/locations` example: `2840` */
     location_code?: string | undefined;
-    /** full name of search engine language optional field default value: English if you use this field, you don’t need to specify language_code you can receive the list of available languages of the search engine with their language_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: English */
+    /** *full name of search engine language* optional field default value: `English` if you use this field, you don't need to specify `language_code` you can receive the list of available languages of the search engine with their `language_name` by making a separate request to `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `English` */
     language_name?: string | undefined;
-    /** search engine language code optional field default value: en 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 https://api.dataforseo.com/v3/keywords_data/google_trends/languages example: en */
+    /** *search engine language code* optional field default value: `en` 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 `https://api.dataforseo.com/v3/keywords_data/google_trends/languages` example: `en` */
     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* 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` */
     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' */
+    /** *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_hour, past_4_hours, past_day, past_7_days, past_30_days, past_90_days, past_12_months, past_5_years possible values for web only: 2004_present possible values for news, youtube, images, froogle: 2008_present */
+    /** *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_hour`, `past_4_hours`, `past_day`, `past_7_days`, `past_30_days`, `past_90_days`, `past_12_months`, `past_5_years` *possible values for `web` only:* `2004_present` *possible values for `news`, `youtube`, `images`, `froogle`:* `2008_present` */
     time_range?: string | undefined;
-    /** types of items returned optional field to speed up the execution of the request, specify one item at a time; possible values: 'google_trends_graph', 'google_trends_map', 'google_trends_topics_list','google_trends_queries_list' default value: 'google_trends_graph' Note: to obtain google_trends_topics_list and google_trends_queries_list items, specify no more than 1 keyword in the keywords field */
+    /** *types of items returned* optional field to speed up the execution of the request, specify one item at a time; possible values: `'google_trends_graph'`, `'google_trends_map'`, `'google_trends_topics_list'`,`'google_trends_queries_list'` default value: `'google_trends_graph'` **Note:** to obtain `google_trends_topics_list` and `google_trends_queries_list` items, specify no more than 1 keyword in the `keywords` field */
     item_types?: string[] | undefined;
-    /** URL for sending task results optional field once the task is completed, we will send a POST request with its results compressed in the gzip format to the postback_url you specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request. example: http://your-server.com/postbackscript?id=$id http://your-server.com/postbackscript?id=$id&tag=$tag Note: special characters in postback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center */
+    /** *URL for sending task results* optional field once the task is completed, we will send a POST request with its results compressed in the `gzip` format to the `postback_url` you specified you can use the ‘$id’ string as a `$id` variable and ‘$tag’ as urlencoded `$tag` variable. We will set the necessary values before sending the request. example: `http://your-server.com/postbackscript?id=$id` `http://your-server.com/postbackscript?id=$id&tag=$tag` **Note:** special characters in `postback_url` will be urlencoded; i.a., the `#` character will be encoded into `%23` learn more on our [Help Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api) */
     postback_url?: string | undefined;
-    /** notification URL of a completed task optional field when a task is completed we will notify you by GET request sent to the URL you have specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request example: http://your-server.com/pingscript?id=$id http://your-server.com/pingscript?id=$id&tag=$tag Note: special characters in pingback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center */
+    /** *notification URL of a completed task* optional field when a task is completed we will notify you by GET request sent to the URL you have specified you can use the ‘$id’ string as a `$id` variable and ‘$tag’ as urlencoded `$tag` variable. We will set the necessary values before sending the request example: `http://your-server.com/pingscript?id=$id` `http://your-server.com/pingscript?id=$id&tag=$tag` **Note:** special characters in `pingback_url` will be urlencoded; i.a., the `#` character will be encoded into `%23` learn more on our [Help Center](https://dataforseo.com/help-center/pingbacks-postbacks-with-dataforseo-api) */
     pingback_url?: 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?: IKeywordsDataGoogleTrendsExploreTaskPostRequestInfo);

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

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

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

@@ -1,11 +1,11 @@
 import { BaseResponseTaskInfo, IBaseResponseTaskInfo } from "./BaseResponseTaskInfo";
 export interface IKeywordsDataGoogleTrendsExploreTaskPostTaskInfo extends IBaseResponseTaskInfo {
-    /** array of results in this case, the value will be null */
+    /** *array of results* in this case, the value will be `null` */
     result?: any | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreTaskPostTaskInfo extends BaseResponseTaskInfo implements IKeywordsDataGoogleTrendsExploreTaskPostTaskInfo {
-    /** array of results in this case, the value will be null */
+    /** *array of results* in this case, the value will be `null` */
     result?: any | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataGoogleTrendsExploreTaskPostTaskInfo);

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

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

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

@@ -1,28 +1,26 @@
 export interface IKeywordsDataGoogleTrendsExploreTasksReadyResultInfo {
-    /** task identifier of the completed task unique task identifier in our system in the UUID format */
+    /** *task identifier of the completed task* **unique task identifier in our system in the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) format** */
     id?: string | undefined;
-    /** search engine specified when setting the task */
+    /** *search engine specified when setting the task* */
     se?: string | undefined;
     se_type?: string | undefined;
-    /** date when the task was posted (in the UTC format) */
+    /** *date when the task was posted (in the UTC format)* */
     date_posted?: string | undefined;
-    /** user-defined task identifier */
     tag?: string | undefined;
-    /** URL for collecting the results of the task */
+    /** *URL for collecting the results of the task* */
     endpoint?: string | undefined;
     [key: string]: any;
 }
 export declare class KeywordsDataGoogleTrendsExploreTasksReadyResultInfo implements IKeywordsDataGoogleTrendsExploreTasksReadyResultInfo {
-    /** task identifier of the completed task unique task identifier in our system in the UUID format */
+    /** *task identifier of the completed task* **unique task identifier in our system in the [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) format** */
     id?: string | undefined;
-    /** search engine specified when setting the task */
+    /** *search engine specified when setting the task* */
     se?: string | undefined;
     se_type?: string | undefined;
-    /** date when the task was posted (in the UTC format) */
+    /** *date when the task was posted (in the UTC format)* */
     date_posted?: string | undefined;
-    /** user-defined task identifier */
     tag?: string | undefined;
-    /** URL for collecting the results of the task */
+    /** *URL for collecting the results of the task* */
     endpoint?: string | undefined;
     [key: string]: any;
     constructor(data?: IKeywordsDataGoogleTrendsExploreTasksReadyResultInfo);

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

@@ -1 +1 @@
-{"version":3,"file":"KeywordsDataGoogleTrendsExploreTasksReadyResultInfo.js","sourceRoot":"","sources":["../../../src/models/KeywordsDataGoogleTrendsExploreTasksReadyResultInfo.ts"],"names":[],"mappings":"AAuBA,MAAM,OAAO,mDAAmD;IAgC5D,YAAY,IAA2D;QAEvE,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,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC;YACrB,IAAI,CAAC,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC;YACrB,IAAI,CAAC,OAAO,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC;YAC/B,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC,aAAa,CAAC,CAAC;YACvC,IAAI,CAAC,GAAG,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC;YACvB,IAAI,CAAC,QAAQ,GAAG,IAAI,CAAC,UAAU,CAAC,CAAC;QACrC,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,mDAAmD,EAAE,CAAC;QACvE,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,IAAI,CAAC,GAAG,IAAI,CAAC,EAAE,CAAC;QACrB,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC,EAAE,CAAC;QACrB,IAAI,CAAC,SAAS,CAAC,GAAG,IAAI,CAAC,OAAO,CAAC;QAC/B,IAAI,CAAC,aAAa,CAAC,GAAG,IAAI,CAAC,WAAW,CAAC;QACvC,IAAI,CAAC,KAAK,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC;QACvB,IAAI,CAAC,UAAU,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC;QACjC,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}
+{"version":3,"file":"KeywordsDataGoogleTrendsExploreTasksReadyResultInfo.js","sourceRoot":"","sources":["../../../src/models/KeywordsDataGoogleTrendsExploreTasksReadyResultInfo.ts"],"names":[],"mappings":"AAsBA,MAAM,OAAO,mDAAmD;IA6B5D,YAAY,IAA2D;QAEvE,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,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC;YACrB,IAAI,CAAC,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,CAAC;YACrB,IAAI,CAAC,OAAO,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC;YAC/B,IAAI,CAAC,WAAW,GAAG,IAAI,CAAC,aAAa,CAAC,CAAC;YACvC,IAAI,CAAC,GAAG,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC;YACvB,IAAI,CAAC,QAAQ,GAAG,IAAI,CAAC,UAAU,CAAC,CAAC;QACrC,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,mDAAmD,EAAE,CAAC;QACvE,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,IAAI,CAAC,GAAG,IAAI,CAAC,EAAE,CAAC;QACrB,IAAI,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC,EAAE,CAAC;QACrB,IAAI,CAAC,SAAS,CAAC,GAAG,IAAI,CAAC,OAAO,CAAC;QAC/B,IAAI,CAAC,aAAa,CAAC,GAAG,IAAI,CAAC,WAAW,CAAC;QACvC,IAAI,CAAC,KAAK,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC;QACvB,IAAI,CAAC,UAAU,CAAC,GAAG,IAAI,CAAC,QAAQ,CAAC;QACjC,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ"}

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

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