dataforseo-client 2.1.2 → 2.1.3

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

@@ -1,62 +1,62 @@
 export interface IDomainAnalyticsTechnologiesAggregationTechnologiesLiveRequestInfo {
-    /** id of the target technology group required field if you don’t specify technology, category or keyword at least one field (group, category, keyword, technology) must be set you can find the full list of technology group ids on this page example: 'marketing' */
+    /** *id of the target technology group* **required field if you don't specify `technology`, `category` or `keyword`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) example: `'marketing'` */
     group?: string | undefined;
-    /** id of the target technology category required field if you don’t specify group, keyword or technology at least one field (group, category, keyword, technology) must be set you can find the full list of technology category ids on this page example: 'crm' */
+    /** *id of the target technology category* **required field if you don't specify `group`, `keyword` or `technology`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) example: `'crm'` */
     category?: string | undefined;
-    /** target technology required field if you don’t specify group, keyword or category at least one field (group, category, keyword, technology) must be set you can find the full list of technologies on this page example: 'Salesforce' */
+    /** *target technology* **required field if you don't specify `group`, `keyword` or `category`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technologies [on this page](/v3/domain_analytics/technologies/technologies) example: `'Salesforce'` */
     technology?: string | undefined;
-    /** target keyword in the domain’s meta keywords required field if you don’t specify group, category or technology at least one field (group, category, keyword, technology) must be set UTF-8 encoding example: 'seo'learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *target keyword in the domain's meta keywords* **required field if you don't specify `group`, `category` or `technology`** at least one field (`group`, `category`, `keyword`, `technology`) must be set UTF-8 encoding example: `'seo'`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) */
     keyword?: string | undefined;
-    /** search mode optional field possible search mode types: as_is – search for results exactly matching the specified group ids, category ids, or technology names entry – search for results matching a part of the specified group ids, category ids, or technology names default value: as_is */
+    /** *search mode* optional field possible search mode types: `as_is` - search for results exactly matching the specified group ids, category ids, or technology names `entry` - search for results matching a part of the specified group ids, category ids, or technology names default value: `as_is` */
     mode?: string | undefined;
-    /** array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: , >=, =, <>, in, not_in, like,not_like you can use the % operator with like and not_like to match any string of zero or more characters you can use the following parameters to filter the results: domain_rank, last_visited, country_iso_code, language_code, content_language_code Note: all filtering parameters are taken from the domain_technology_item of the domain_technologies endpoint; example: [['country_iso_code','=','US'], 'and', ['domain_rank','>',800]]for more information about filters, please refer to Domain Analytics Technologies API – Filters */
+    /** *array of results filtering parameters* optional field **you can add several filters at once (8 filters maximum)** you should set a logical operator `and`, `or` between the conditions the following operators are supported: ``, `>=`, `=`, `<>`, `in`, `not_in`, `like`,`not_like` you can use the `%` operator with `like` and `not_like` to match any string of zero or more characters you can use the following parameters to filter the results: `domain_rank`, `last_visited`, `country_iso_code`, `language_code`, `content_language_code` **Note:** all filtering parameters are taken from the `domain_technology_item` of the [domain_technologies](/v3/domain_analytics/technologies/filters) endpoint; example: `[['country_iso_code','=','US'],'and',['domain_rank','>',800]]`for more information about filters, please refer to [Domain Analytics Technologies API - Filters](/v3/domain_analytics/technologies/filters) */
     filters?: any[] | undefined;
-    /** results sorting rules optional field you can use the following values to sort the results: groups_count, categories_count, technologies_count possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ['groups_count,desc'] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ['groups_count,desc','technologies_count,desc'] default value: ['groups_count,desc','categories_count,desc','technologies_count,desc'] */
+    /** *results sorting rules* optional field you can use the following values to sort the results: `groups_count`, `categories_count`, `technologies_count` possible sorting types: `asc` - results will be sorted in the ascending order `desc` - results will be sorted in the descending order you should use a comma to set up a sorting type example: `['groups_count,desc']` **note that you can set no more than three sorting rules in a single request** you should use a comma to separate several sorting rules example: `['groups_count,desc','technologies_count,desc']` default value: `['groups_count,desc','categories_count,desc','technologies_count,desc']` */
     order_by?: string[] | undefined;
-    /** maximum number of returned technology groups optional field you can use this field to limit the number of items with identical 'group' in the results default value: 5 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technology groups* optional field you can use this field to limit the number of items with identical `'group'` in the results default value: `5` minimum value: `1` maximum value: `10000` */
     internal_groups_list_limit?: number | undefined;
-    /** maximum number of returned technology categories within the same group optional field you can use this field to limit the number of items with identical 'category' in the results default value: 5 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technology categories within the same group* optional field you can use this field to limit the number of items with identical `'category'` in the results default value: `5` minimum value: `1` maximum value: `10000` */
     internal_categories_list_limit?: number | undefined;
-    /** maximum number of returned technologies within the same category optional field you can use this field to limit the number of items with identical 'technology' in the results default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technologies within the same category* optional field you can use this field to limit the number of items with identical `'technology'` in the results default value: `10` minimum value: `1` maximum value: `10000` */
     internal_technologies_list_limit?: number | undefined;
-    /** maximum number of items with identical 'category', 'group', and 'technology' optional field if you use this field, the values specified in internal_groups_list_limit, internal_categories_list_limit and internal_technologies_list_limit will be ignored; you can use this field to limit the number of items with identical 'category', 'group', or 'technology' default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of items with identical `'category'`, `'group'`, and `'technology'`* optional field if you use this field, the values specified in `internal_groups_list_limit`, `internal_categories_list_limit` and `internal_technologies_list_limit` will be ignored; you can use this field to limit the number of items with identical `'category'`, `'group'`, or `'technology'` default value: `10` minimum value: `1` maximum value: `10000` */
     internal_list_limit?: number | undefined;
-    /** the maximum number of returned technologies optional field default value: 100 maximum value: 10000 */
+    /** *the maximum number of returned technologies* optional field default value: `100` maximum value: `10000` */
     limit?: number | undefined;
-    /** offset in the results array of returned domains optional field default value: 0 maximum value: 9999 if you specify the 10 value, the first ten technologies in the results array will be omitted and the data will be provided for the successive technologies */
+    /** *offset in the results array of returned domains* optional field default value: `0` maximum value: `9999` if you specify the `10` value, the first ten technologies in the results array will be omitted and the data will be provided for the successive technologies */
     offset?: number | 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 DomainAnalyticsTechnologiesAggregationTechnologiesLiveRequestInfo implements IDomainAnalyticsTechnologiesAggregationTechnologiesLiveRequestInfo {
-    /** id of the target technology group required field if you don’t specify technology, category or keyword at least one field (group, category, keyword, technology) must be set you can find the full list of technology group ids on this page example: 'marketing' */
+    /** *id of the target technology group* **required field if you don't specify `technology`, `category` or `keyword`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) example: `'marketing'` */
     group?: string | undefined;
-    /** id of the target technology category required field if you don’t specify group, keyword or technology at least one field (group, category, keyword, technology) must be set you can find the full list of technology category ids on this page example: 'crm' */
+    /** *id of the target technology category* **required field if you don't specify `group`, `keyword` or `technology`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) example: `'crm'` */
     category?: string | undefined;
-    /** target technology required field if you don’t specify group, keyword or category at least one field (group, category, keyword, technology) must be set you can find the full list of technologies on this page example: 'Salesforce' */
+    /** *target technology* **required field if you don't specify `group`, `keyword` or `category`** at least one field (`group`, `category`, `keyword`, `technology`) must be set you can find the full list of technologies [on this page](/v3/domain_analytics/technologies/technologies) example: `'Salesforce'` */
     technology?: string | undefined;
-    /** target keyword in the domain’s meta keywords required field if you don’t specify group, category or technology at least one field (group, category, keyword, technology) must be set UTF-8 encoding example: 'seo'learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *target keyword in the domain's meta keywords* **required field if you don't specify `group`, `category` or `technology`** at least one field (`group`, `category`, `keyword`, `technology`) must be set UTF-8 encoding example: `'seo'`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) */
     keyword?: string | undefined;
-    /** search mode optional field possible search mode types: as_is – search for results exactly matching the specified group ids, category ids, or technology names entry – search for results matching a part of the specified group ids, category ids, or technology names default value: as_is */
+    /** *search mode* optional field possible search mode types: `as_is` - search for results exactly matching the specified group ids, category ids, or technology names `entry` - search for results matching a part of the specified group ids, category ids, or technology names default value: `as_is` */
     mode?: string | undefined;
-    /** array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: , >=, =, <>, in, not_in, like,not_like you can use the % operator with like and not_like to match any string of zero or more characters you can use the following parameters to filter the results: domain_rank, last_visited, country_iso_code, language_code, content_language_code Note: all filtering parameters are taken from the domain_technology_item of the domain_technologies endpoint; example: [['country_iso_code','=','US'], 'and', ['domain_rank','>',800]]for more information about filters, please refer to Domain Analytics Technologies API – Filters */
+    /** *array of results filtering parameters* optional field **you can add several filters at once (8 filters maximum)** you should set a logical operator `and`, `or` between the conditions the following operators are supported: ``, `>=`, `=`, `<>`, `in`, `not_in`, `like`,`not_like` you can use the `%` operator with `like` and `not_like` to match any string of zero or more characters you can use the following parameters to filter the results: `domain_rank`, `last_visited`, `country_iso_code`, `language_code`, `content_language_code` **Note:** all filtering parameters are taken from the `domain_technology_item` of the [domain_technologies](/v3/domain_analytics/technologies/filters) endpoint; example: `[['country_iso_code','=','US'],'and',['domain_rank','>',800]]`for more information about filters, please refer to [Domain Analytics Technologies API - Filters](/v3/domain_analytics/technologies/filters) */
     filters?: any[] | undefined;
-    /** results sorting rules optional field you can use the following values to sort the results: groups_count, categories_count, technologies_count possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ['groups_count,desc'] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ['groups_count,desc','technologies_count,desc'] default value: ['groups_count,desc','categories_count,desc','technologies_count,desc'] */
+    /** *results sorting rules* optional field you can use the following values to sort the results: `groups_count`, `categories_count`, `technologies_count` possible sorting types: `asc` - results will be sorted in the ascending order `desc` - results will be sorted in the descending order you should use a comma to set up a sorting type example: `['groups_count,desc']` **note that you can set no more than three sorting rules in a single request** you should use a comma to separate several sorting rules example: `['groups_count,desc','technologies_count,desc']` default value: `['groups_count,desc','categories_count,desc','technologies_count,desc']` */
     order_by?: string[] | undefined;
-    /** maximum number of returned technology groups optional field you can use this field to limit the number of items with identical 'group' in the results default value: 5 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technology groups* optional field you can use this field to limit the number of items with identical `'group'` in the results default value: `5` minimum value: `1` maximum value: `10000` */
     internal_groups_list_limit?: number | undefined;
-    /** maximum number of returned technology categories within the same group optional field you can use this field to limit the number of items with identical 'category' in the results default value: 5 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technology categories within the same group* optional field you can use this field to limit the number of items with identical `'category'` in the results default value: `5` minimum value: `1` maximum value: `10000` */
     internal_categories_list_limit?: number | undefined;
-    /** maximum number of returned technologies within the same category optional field you can use this field to limit the number of items with identical 'technology' in the results default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of returned technologies within the same category* optional field you can use this field to limit the number of items with identical `'technology'` in the results default value: `10` minimum value: `1` maximum value: `10000` */
     internal_technologies_list_limit?: number | undefined;
-    /** maximum number of items with identical 'category', 'group', and 'technology' optional field if you use this field, the values specified in internal_groups_list_limit, internal_categories_list_limit and internal_technologies_list_limit will be ignored; you can use this field to limit the number of items with identical 'category', 'group', or 'technology' default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of items with identical `'category'`, `'group'`, and `'technology'`* optional field if you use this field, the values specified in `internal_groups_list_limit`, `internal_categories_list_limit` and `internal_technologies_list_limit` will be ignored; you can use this field to limit the number of items with identical `'category'`, `'group'`, or `'technology'` default value: `10` minimum value: `1` maximum value: `10000` */
     internal_list_limit?: number | undefined;
-    /** the maximum number of returned technologies optional field default value: 100 maximum value: 10000 */
+    /** *the maximum number of returned technologies* optional field default value: `100` maximum value: `10000` */
     limit?: number | undefined;
-    /** offset in the results array of returned domains optional field default value: 0 maximum value: 9999 if you specify the 10 value, the first ten technologies in the results array will be omitted and the data will be provided for the successive technologies */
+    /** *offset in the results array of returned domains* optional field default value: `0` maximum value: `9999` if you specify the `10` value, the first ten technologies in the results array will be omitted and the data will be provided for the successive technologies */
     offset?: number | 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?: IDomainAnalyticsTechnologiesAggregationTechnologiesLiveRequestInfo);

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

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

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

@@ -1,8 +1,8 @@
 import { DomainAnalyticsTechnologiesAggregationTechnologiesLiveItem } from "./DomainAnalyticsTechnologiesAggregationTechnologiesLiveItem";
 export interface IDomainAnalyticsTechnologiesAggregationTechnologiesLiveResultInfo {
-    /** total amount of results in our database relevant to your request */
+    /** *total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
     /** offset in the results array of returned domains */
     offset?: number | undefined;
@@ -10,9 +10,9 @@ export interface IDomainAnalyticsTechnologiesAggregationTechnologiesLiveResultIn
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesAggregationTechnologiesLiveResultInfo implements IDomainAnalyticsTechnologiesAggregationTechnologiesLiveResultInfo {
-    /** total amount of results in our database relevant to your request */
+    /** *total amount of results in our database relevant to your request* */
     total_count?: number | undefined;
-    /** the number of results returned in the items array */
+    /** *the number of results returned in the `items` array* */
     items_count?: number | undefined;
     /** offset in the results array of returned domains */
     offset?: number | undefined;

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

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

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

@@ -1,10 +1,10 @@
 export interface IDomainAnalyticsTechnologiesDomainTechnologiesLiveRequestInfo {
-    /** target domain required field domain name of the website to analyze Note: results will be returned for the specified domain only */
+    /** *target domain* **required field** domain name of the website to analyze **Note:** results will be returned for the specified domain only */
     target?: string | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesDomainTechnologiesLiveRequestInfo implements IDomainAnalyticsTechnologiesDomainTechnologiesLiveRequestInfo {
-    /** target domain required field domain name of the website to analyze Note: results will be returned for the specified domain only */
+    /** *target domain* **required field** domain name of the website to analyze **Note:** results will be returned for the specified domain only */
     target?: string | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesDomainTechnologiesLiveRequestInfo);

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

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

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

@@ -2,62 +2,62 @@ import { TechnologiesInfo } from "./TechnologiesInfo";
 export interface IDomainAnalyticsTechnologiesDomainTechnologiesLiveResultInfo {
     /** type of element */
     type?: string | undefined;
-    /** specified domain name */
+    /** *specified domain name* */
     domain?: string | undefined;
-    /** domain meta title */
+    /** *domain meta title* */
     title?: string | undefined;
-    /** domain meta description */
+    /** *domain meta description* */
     description?: string | undefined;
-    /** domain meta keywords */
+    /** *domain meta keywords* */
     meta_keywords?: string[] | undefined;
-    /** backlink rank of the target domain learn more about the metric and how it is calculated in this help center article */
+    /** *backlink rank of the target domain* learn more about the metric and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domain_rank?: number | undefined;
-    /** most recent date when our crawler visited the domain in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2022-10-10 12:57:46 +00:00 */
+    /** *most recent date when our crawler visited the domain* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2022-10-10 12:57:46 +00:00` */
     last_visited?: string | undefined;
-    /** domain ISO code ISO code of the country that the target domain is determined to belong to */
+    /** *domain ISO code* ISO code of the country that the target domain is determined to belong to */
     country_iso_code?: string | undefined;
-    /** domain language code of the language that the target domain is determined to be associated with */
+    /** *domain language* code of the language that the target domain is determined to be associated with */
     language_code?: string | undefined;
-    /** content language code of the language that content on the target domain is written in */
+    /** *content language* code of the language that content on the target domain is written in */
     content_language_code?: string | undefined;
-    /** phone numbers of the target contact phone numbers indicated on the target website */
+    /** *phone numbers of the target* contact phone numbers indicated on the target website */
     phone_numbers?: string[] | undefined;
-    /** emails of the target emails indicated on the target website */
+    /** *emails of the target* emails indicated on the target website */
     emails?: string[] | undefined;
-    /** social media links and handles social media URLs detected in the social graphs of the target website */
+    /** *social media links and handles* social media URLs detected in the social graphs of the target website */
     social_graph_urls?: string[] | undefined;
-    /** technologies used by target domain contains objects with the names of technologies used on the website see the full list of available technologies structured by groups and categories */
+    /** *technologies used by target domain* contains objects with the names of technologies used on the website [see the full list of available technologies structured by groups and categories](/v3/domain_analytics/technologies/technologies/) */
     technologies?: TechnologiesInfo | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesDomainTechnologiesLiveResultInfo implements IDomainAnalyticsTechnologiesDomainTechnologiesLiveResultInfo {
     /** type of element */
     type?: string | undefined;
-    /** specified domain name */
+    /** *specified domain name* */
     domain?: string | undefined;
-    /** domain meta title */
+    /** *domain meta title* */
     title?: string | undefined;
-    /** domain meta description */
+    /** *domain meta description* */
     description?: string | undefined;
-    /** domain meta keywords */
+    /** *domain meta keywords* */
     meta_keywords?: string[] | undefined;
-    /** backlink rank of the target domain learn more about the metric and how it is calculated in this help center article */
+    /** *backlink rank of the target domain* learn more about the metric and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domain_rank?: number | undefined;
-    /** most recent date when our crawler visited the domain in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2022-10-10 12:57:46 +00:00 */
+    /** *most recent date when our crawler visited the domain* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2022-10-10 12:57:46 +00:00` */
     last_visited?: string | undefined;
-    /** domain ISO code ISO code of the country that the target domain is determined to belong to */
+    /** *domain ISO code* ISO code of the country that the target domain is determined to belong to */
     country_iso_code?: string | undefined;
-    /** domain language code of the language that the target domain is determined to be associated with */
+    /** *domain language* code of the language that the target domain is determined to be associated with */
     language_code?: string | undefined;
-    /** content language code of the language that content on the target domain is written in */
+    /** *content language* code of the language that content on the target domain is written in */
     content_language_code?: string | undefined;
-    /** phone numbers of the target contact phone numbers indicated on the target website */
+    /** *phone numbers of the target* contact phone numbers indicated on the target website */
     phone_numbers?: string[] | undefined;
-    /** emails of the target emails indicated on the target website */
+    /** *emails of the target* emails indicated on the target website */
     emails?: string[] | undefined;
-    /** social media links and handles social media URLs detected in the social graphs of the target website */
+    /** *social media links and handles* social media URLs detected in the social graphs of the target website */
     social_graph_urls?: string[] | undefined;
-    /** technologies used by target domain contains objects with the names of technologies used on the website see the full list of available technologies structured by groups and categories */
+    /** *technologies used by target domain* contains objects with the names of technologies used on the website [see the full list of available technologies structured by groups and categories](/v3/domain_analytics/technologies/technologies/) */
     technologies?: TechnologiesInfo | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesDomainTechnologiesLiveResultInfo);

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

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

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

@@ -1,38 +1,38 @@
 export interface IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveRequestInfo {
-    /** target search terms required field specify target HTML elements, tags, attributes, their content or all of the above if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HTML code of their homepage maximum number of search terms you can specify: 10 example: ['data-attrid'] */
+    /** *target search terms* **required field** specify target HTML elements, tags, attributes, their content or all of the above if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HTML code of their homepage maximum number of search terms you can specify: 10 example: `['data-attrid']` */
     search_terms?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords optional field UTF-8 encoding maximum number of keywords you can specify: 10 example: ['seo','software'] learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *target keywords in the domain's title, description or meta keywords* optional field UTF-8 encoding maximum number of keywords you can specify: 10  example: `['seo','software']` 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;
-    /** search mode optional field possible search mode types: strict_entry – search for results exactly matching the order, intervals and separators in the specified search terms entry – search for results ignoring the order, intervals and separators in the specified search terms default value: entry */
+    /** *search mode* optional field possible search mode types: `strict_entry` - search for results exactly matching the order, intervals and separators in the specified search terms `entry` - search for results ignoring the order, intervals and separators in the specified search terms default value: `entry` */
     mode?: string | undefined;
-    /** array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: , >=, =, <>, in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: ['domain','like','%seo%'] [['country_iso_code','=','US'], 'and', ['domain_rank','>',100]] [['domain_rank','>',100], 'and', [['country_iso_code','=','US'],'or',['country_iso_code','=','CA']]] for more information about filters, please refer to Domain Analytics Technologies API – Filters */
+    /** *array of results filtering parameters* optional field **you can add several filters at once (8 filters maximum)** you should set a logical operator `and`, `or` between the conditions the following operators are supported: ``, `>=`, `=`, `<>`, `in`, `not_in`, `like`, `not_like` you can use the `%` operator with `like` and `not_like` to match any string of zero or more characters example: `['domain','like','%seo%']` `[['country_iso_code','=','US'],'and',['domain_rank','>',100]]` `[['domain_rank','>',100],'and',[['country_iso_code','=','US'],'or',['country_iso_code','=','CA']]]` for more information about filters, please refer to [Domain Analytics Technologies API - Filters](/v3/domain_analytics/technologies/filters) */
     filters?: any[] | undefined;
-    /** results sorting rules optional field available fields: domain_rank, domain, last_visited, country_iso_code, language_code, content_language_code possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ['last_visited,desc'] default rule: ['domain_rank,desc'] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ['last_visited,desc','domain_rank,desc'] */
+    /** *results sorting rules* optional field available fields:  `domain_rank`, `domain`, `last_visited`, `country_iso_code`, `language_code`, `content_language_code` possible sorting types: `asc` - results will be sorted in the ascending order `desc` - results will be sorted in the descending order you should use a comma to set up a sorting type example: `['last_visited,desc']` default rule: `['domain_rank,desc']` **note that you can set no more than three sorting rules in a single request** you should use a comma to separate several sorting rules example: `['last_visited,desc','domain_rank,desc']` */
     order_by?: string[] | undefined;
-    /** the maximum number of returned domains optional field default value: 100 maximum value: 10000 */
+    /** *the maximum number of returned domains* optional field default value: `100` maximum value: `10000` */
     limit?: number | undefined;
-    /** offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains; Note: the maximum value is 9999, the sum of limit and offset must not exceed 10000; use the offset_token if you would like to offset more results */
+    /** *offset in the results array of returned domains* optional field default value: `0` if you specify the `10` value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains; **Note:** the maximum value is `9999`, the sum of `limit` and `offset` must not exceed `10000`; use the `offset_token` if you would like to offset more results */
     offset?: number | undefined;
-    /** token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request; by specifying the unique offset_token value from the response array, you will get the subsequent results of the initial task; offset_token values are unique for each subsequent task Note: if the offset_token is specified in the request, all other parameters should be identical to the previous request learn more about this parameter on our Help Center */
+    /** *token for subsequent requests* optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request; by specifying the unique `offset_token` value from the response array, you will get the subsequent results of the initial task; `offset_token` values are unique for each subsequent task  **Note:** if the `offset_token` is specified in the request, all other parameters should be identical to the previous request learn more about this parameter on our [Help Center](https://dataforseo.com/help-center/what-is-the-difference-between-the-offset-and-offset_token-parameters#offset_token) */
     offset_token?: string | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesDomainsByHtmlTermsLiveRequestInfo implements IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveRequestInfo {
-    /** target search terms required field specify target HTML elements, tags, attributes, their content or all of the above if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HTML code of their homepage maximum number of search terms you can specify: 10 example: ['data-attrid'] */
+    /** *target search terms* **required field** specify target HTML elements, tags, attributes, their content or all of the above if you specify more than one search term, you will receive only the domains containing all of the specified terms in the HTML code of their homepage maximum number of search terms you can specify: 10 example: `['data-attrid']` */
     search_terms?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords optional field UTF-8 encoding maximum number of keywords you can specify: 10 example: ['seo','software'] learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article */
+    /** *target keywords in the domain's title, description or meta keywords* optional field UTF-8 encoding maximum number of keywords you can specify: 10  example: `['seo','software']` 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;
-    /** search mode optional field possible search mode types: strict_entry – search for results exactly matching the order, intervals and separators in the specified search terms entry – search for results ignoring the order, intervals and separators in the specified search terms default value: entry */
+    /** *search mode* optional field possible search mode types: `strict_entry` - search for results exactly matching the order, intervals and separators in the specified search terms `entry` - search for results ignoring the order, intervals and separators in the specified search terms default value: `entry` */
     mode?: string | undefined;
-    /** array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: , >=, =, <>, in, not_in, like, not_like you can use the % operator with like and not_like to match any string of zero or more characters example: ['domain','like','%seo%'] [['country_iso_code','=','US'], 'and', ['domain_rank','>',100]] [['domain_rank','>',100], 'and', [['country_iso_code','=','US'],'or',['country_iso_code','=','CA']]] for more information about filters, please refer to Domain Analytics Technologies API – Filters */
+    /** *array of results filtering parameters* optional field **you can add several filters at once (8 filters maximum)** you should set a logical operator `and`, `or` between the conditions the following operators are supported: ``, `>=`, `=`, `<>`, `in`, `not_in`, `like`, `not_like` you can use the `%` operator with `like` and `not_like` to match any string of zero or more characters example: `['domain','like','%seo%']` `[['country_iso_code','=','US'],'and',['domain_rank','>',100]]` `[['domain_rank','>',100],'and',[['country_iso_code','=','US'],'or',['country_iso_code','=','CA']]]` for more information about filters, please refer to [Domain Analytics Technologies API - Filters](/v3/domain_analytics/technologies/filters) */
     filters?: any[] | undefined;
-    /** results sorting rules optional field available fields: domain_rank, domain, last_visited, country_iso_code, language_code, content_language_code possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ['last_visited,desc'] default rule: ['domain_rank,desc'] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ['last_visited,desc','domain_rank,desc'] */
+    /** *results sorting rules* optional field available fields:  `domain_rank`, `domain`, `last_visited`, `country_iso_code`, `language_code`, `content_language_code` possible sorting types: `asc` - results will be sorted in the ascending order `desc` - results will be sorted in the descending order you should use a comma to set up a sorting type example: `['last_visited,desc']` default rule: `['domain_rank,desc']` **note that you can set no more than three sorting rules in a single request** you should use a comma to separate several sorting rules example: `['last_visited,desc','domain_rank,desc']` */
     order_by?: string[] | undefined;
-    /** the maximum number of returned domains optional field default value: 100 maximum value: 10000 */
+    /** *the maximum number of returned domains* optional field default value: `100` maximum value: `10000` */
     limit?: number | undefined;
-    /** offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains; Note: the maximum value is 9999, the sum of limit and offset must not exceed 10000; use the offset_token if you would like to offset more results */
+    /** *offset in the results array of returned domains* optional field default value: `0` if you specify the `10` value, the first ten domains in the results array will be omitted and the data will be provided for the successive domains; **Note:** the maximum value is `9999`, the sum of `limit` and `offset` must not exceed `10000`; use the `offset_token` if you would like to offset more results */
     offset?: number | undefined;
-    /** token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request; by specifying the unique offset_token value from the response array, you will get the subsequent results of the initial task; offset_token values are unique for each subsequent task Note: if the offset_token is specified in the request, all other parameters should be identical to the previous request learn more about this parameter on our Help Center */
+    /** *token for subsequent requests* optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 100,000 results in a single request; by specifying the unique `offset_token` value from the response array, you will get the subsequent results of the initial task; `offset_token` values are unique for each subsequent task  **Note:** if the `offset_token` is specified in the request, all other parameters should be identical to the previous request learn more about this parameter on our [Help Center](https://dataforseo.com/help-center/what-is-the-difference-between-the-offset-and-offset_token-parameters#offset_token) */
     offset_token?: string | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveRequestInfo);

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

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

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

@@ -1,27 +1,27 @@
 import { DomainAnalyticsTechnologiesDomainsByLiveItem } from "./DomainAnalyticsTechnologiesDomainsByLiveItem";
 export interface IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveResultInfo {
-    /** total number of relevant items in the database */
+    /** *total number of relevant items in the database* */
     total_count?: number | undefined;
-    /** number of items in the results array */
+    /** *number of items in the results array* */
     items_count?: number | undefined;
-    /** specified offset value */
+    /** *specified offset value* */
     offset?: number | undefined;
-    /** token for subsequent requests by specifying the unique offset_token when setting a new task, you will get the subsequent results of the initial task; offset_token values are unique for each subsequent task */
+    /** *token for subsequent requests* by specifying the unique `offset_token` when setting a new task, you will get the subsequent results of the initial task; `offset_token` values are unique for each subsequent task */
     offset_token?: string | undefined;
-    /** items array */
+    /** *items array* */
     items?: DomainAnalyticsTechnologiesDomainsByLiveItem[] | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesDomainsByHtmlTermsLiveResultInfo implements IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveResultInfo {
-    /** total number of relevant items in the database */
+    /** *total number of relevant items in the database* */
     total_count?: number | undefined;
-    /** number of items in the results array */
+    /** *number of items in the results array* */
     items_count?: number | undefined;
-    /** specified offset value */
+    /** *specified offset value* */
     offset?: number | undefined;
-    /** token for subsequent requests by specifying the unique offset_token when setting a new task, you will get the subsequent results of the initial task; offset_token values are unique for each subsequent task */
+    /** *token for subsequent requests* by specifying the unique `offset_token` when setting a new task, you will get the subsequent results of the initial task; `offset_token` values are unique for each subsequent task */
     offset_token?: string | undefined;
-    /** items array */
+    /** *items array* */
     items?: DomainAnalyticsTechnologiesDomainsByLiveItem[] | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesDomainsByHtmlTermsLiveResultInfo);

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

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

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

@@ -2,62 +2,62 @@ import { TechnologiesInfo } from "./TechnologiesInfo";
 export interface IDomainAnalyticsTechnologiesDomainsByLiveItem {
     /** type of element */
     type?: string | undefined;
-    /** specified domain name */
+    /** *specified domain name* */
     domain?: string | undefined;
-    /** domain meta title */
+    /** *domain meta title* */
     title?: string | undefined;
-    /** domain meta description */
+    /** *domain meta description* */
     description?: string | undefined;
-    /** domain meta keywords */
+    /** *domain meta keywords* */
     meta_keywords?: string[] | undefined;
-    /** backlink rank of the target domain learn more about the metric and how it is calculated in this help center article */
+    /** *backlink rank of the target domain* learn more about the metric and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domain_rank?: number | undefined;
-    /** most recent date when our crawler visited the domain in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2022-10-10 12:57:46 +00:00 */
+    /** *most recent date when our crawler visited the domain* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2022-10-10 12:57:46 +00:00` */
     last_visited?: string | undefined;
-    /** domain ISO code ISO code of the country that target domain is determined to belong to */
+    /** *domain ISO code* ISO code of the country that target domain is determined to belong to */
     country_iso_code?: string | undefined;
-    /** domain language code of the language that target domain is determined to be associated with */
+    /** *domain language* code of the language that target domain is determined to be associated with */
     language_code?: string | undefined;
-    /** content language code of the language that content on the target domain is written with */
+    /** *content language* code of the language that content on the target domain is written with */
     content_language_code?: string | undefined;
-    /** phone numbers of the target contact phone numbers indicated on the target website */
+    /** *phone numbers of the target* contact phone numbers indicated on the target website */
     phone_numbers?: string[] | undefined;
-    /** emails of the target emails indicated on the target website */
+    /** *emails of the target* emails indicated on the target website */
     emails?: string[] | undefined;
-    /** social media links and handles social media URLs detected in the social graphs of the target website */
+    /** *social media links and handles* social media URLs detected in the social graphs of the target website */
     social_graph_urls?: string[] | undefined;
-    /** technologies used by target domain contains objects with the names of technologies used on the website; to get a full list of technologies and their structure, refer to the technologies endpoint */
+    /** *technologies used by target domain* contains objects with the names of technologies used on the website; to get a full list of technologies and their structure, refer to the [technologies endpoint](/v3/domain_analytics/technologies/technologies/) */
     technologies?: TechnologiesInfo | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesDomainsByLiveItem implements IDomainAnalyticsTechnologiesDomainsByLiveItem {
     /** type of element */
     type?: string | undefined;
-    /** specified domain name */
+    /** *specified domain name* */
     domain?: string | undefined;
-    /** domain meta title */
+    /** *domain meta title* */
     title?: string | undefined;
-    /** domain meta description */
+    /** *domain meta description* */
     description?: string | undefined;
-    /** domain meta keywords */
+    /** *domain meta keywords* */
     meta_keywords?: string[] | undefined;
-    /** backlink rank of the target domain learn more about the metric and how it is calculated in this help center article */
+    /** *backlink rank of the target domain* learn more about the metric and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domain_rank?: number | undefined;
-    /** most recent date when our crawler visited the domain in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2022-10-10 12:57:46 +00:00 */
+    /** *most recent date when our crawler visited the domain* in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: `2022-10-10 12:57:46 +00:00` */
     last_visited?: string | undefined;
-    /** domain ISO code ISO code of the country that target domain is determined to belong to */
+    /** *domain ISO code* ISO code of the country that target domain is determined to belong to */
     country_iso_code?: string | undefined;
-    /** domain language code of the language that target domain is determined to be associated with */
+    /** *domain language* code of the language that target domain is determined to be associated with */
     language_code?: string | undefined;
-    /** content language code of the language that content on the target domain is written with */
+    /** *content language* code of the language that content on the target domain is written with */
     content_language_code?: string | undefined;
-    /** phone numbers of the target contact phone numbers indicated on the target website */
+    /** *phone numbers of the target* contact phone numbers indicated on the target website */
     phone_numbers?: string[] | undefined;
-    /** emails of the target emails indicated on the target website */
+    /** *emails of the target* emails indicated on the target website */
     emails?: string[] | undefined;
-    /** social media links and handles social media URLs detected in the social graphs of the target website */
+    /** *social media links and handles* social media URLs detected in the social graphs of the target website */
     social_graph_urls?: string[] | undefined;
-    /** technologies used by target domain contains objects with the names of technologies used on the website; to get a full list of technologies and their structure, refer to the technologies endpoint */
+    /** *technologies used by target domain* contains objects with the names of technologies used on the website; to get a full list of technologies and their structure, refer to the [technologies endpoint](/v3/domain_analytics/technologies/technologies/) */
     technologies?: TechnologiesInfo | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesDomainsByLiveItem);