dataforseo-client 2.1.2 → 2.1.5

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

@@ -1,50 +1,50 @@
 export interface IDomainAnalyticsTechnologiesDomainsByTechnologyLiveRequestInfo {
-    /** target technology paths required field if you don’t specify groups, technologies, keywords or categories at least one field (technology_paths, groups, technologies, keywords or categories) must be set; each technology path should be specified as a separate object containing “path” and “name”, where “path” is specified as “$group_id.$category_id” and “name” – as the name of the target technology; each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names on this page note: you can specify up to 10 technology paths in this array example: [{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}] */
+    /** *target technology paths* **required field if you don't specify `groups`, `technologies`, `keywords` or `categories`** at least one field (`technology_paths`, `groups`, `technologies`, `keywords` or `categories`) must be set; each technology path should be specified as a separate object containing 'path' and 'name', where 'path' is specified as '$group_id.$category_id' and 'name' - as the name of the target technology;  each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology paths in this array example: `[{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}]` */
     technology_paths?: string[] | undefined;
-    /** ids of the target technology groups required field if you don’t specify technologies, technology_paths, keywords or categories you can find the full list of technology group ids on this page note: you can specify up to 10 technology groups in this array example: ['sales', 'marketing'] */
+    /** *ids of the target technology groups* **required field if you don't specify `technologies`, `technology_paths`, `keywords` or `categories`** you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology groups in this array example: `['sales', 'marketing']` */
     groups?: string[] | undefined;
-    /** ids of the target technology categories required field if you don’t specify groups, technology_paths, keywords or technologies you can find the full list of technology category ids on this page note: you can specify up to 10 technology categories in this array example: ['payment_processors','crm'] */
+    /** *ids of the target technology categories* **required field if you don't specify `groups`, `technology_paths`, `keywords` or `technologies`** you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology categories in this array example: `['payment_processors','crm']` */
     categories?: string[] | undefined;
-    /** target technologies required field if you don’t specify groups, technology_paths, keywords or categories you can find the full list of technologies you can specify here on this page note: you can specify up to 10 technologies in this array example: ['Google Pay','Salesforce'] */
+    /** *target technologies* **required field if you don't specify `groups`, `technology_paths`, `keywords` or `categories`** you can find the full list of technologies you can specify here [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technologies in this array example: `['Google Pay','Salesforce']` */
     technologies?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords required field if you don’t specify groups, technology_paths, technologies or categories optional field you can specify the maximum of 10 keywords; UTF-8 encoding; 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* **required field if you don't specify `groups`, `technology_paths`, `technologies` or `categories`** optional field you can specify the maximum of 10 keywords; UTF-8 encoding; 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: 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 example: ['country_iso_code','=','US'] [['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: `['country_iso_code','=','US']` `[['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 DomainAnalyticsTechnologiesDomainsByTechnologyLiveRequestInfo implements IDomainAnalyticsTechnologiesDomainsByTechnologyLiveRequestInfo {
-    /** target technology paths required field if you don’t specify groups, technologies, keywords or categories at least one field (technology_paths, groups, technologies, keywords or categories) must be set; each technology path should be specified as a separate object containing “path” and “name”, where “path” is specified as “$group_id.$category_id” and “name” – as the name of the target technology; each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names on this page note: you can specify up to 10 technology paths in this array example: [{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}] */
+    /** *target technology paths* **required field if you don't specify `groups`, `technologies`, `keywords` or `categories`** at least one field (`technology_paths`, `groups`, `technologies`, `keywords` or `categories`) must be set; each technology path should be specified as a separate object containing 'path' and 'name', where 'path' is specified as '$group_id.$category_id' and 'name' - as the name of the target technology;  each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology paths in this array example: `[{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}]` */
     technology_paths?: string[] | undefined;
-    /** ids of the target technology groups required field if you don’t specify technologies, technology_paths, keywords or categories you can find the full list of technology group ids on this page note: you can specify up to 10 technology groups in this array example: ['sales', 'marketing'] */
+    /** *ids of the target technology groups* **required field if you don't specify `technologies`, `technology_paths`, `keywords` or `categories`** you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology groups in this array example: `['sales', 'marketing']` */
     groups?: string[] | undefined;
-    /** ids of the target technology categories required field if you don’t specify groups, technology_paths, keywords or technologies you can find the full list of technology category ids on this page note: you can specify up to 10 technology categories in this array example: ['payment_processors','crm'] */
+    /** *ids of the target technology categories* **required field if you don't specify `groups`, `technology_paths`, `keywords` or `technologies`** you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology categories in this array example: `['payment_processors','crm']` */
     categories?: string[] | undefined;
-    /** target technologies required field if you don’t specify groups, technology_paths, keywords or categories you can find the full list of technologies you can specify here on this page note: you can specify up to 10 technologies in this array example: ['Google Pay','Salesforce'] */
+    /** *target technologies* **required field if you don't specify `groups`, `technology_paths`, `keywords` or `categories`** you can find the full list of technologies you can specify here [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technologies in this array example: `['Google Pay','Salesforce']` */
     technologies?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords required field if you don’t specify groups, technology_paths, technologies or categories optional field you can specify the maximum of 10 keywords; UTF-8 encoding; 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* **required field if you don't specify `groups`, `technology_paths`, `technologies` or `categories`** optional field you can specify the maximum of 10 keywords; UTF-8 encoding; 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: 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 example: ['country_iso_code','=','US'] [['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: `['country_iso_code','=','US']` `[['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?: IDomainAnalyticsTechnologiesDomainsByTechnologyLiveRequestInfo);

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

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

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

@@ -1,27 +1,27 @@
 import { DomainAnalyticsTechnologiesDomainsByLiveItem } from "./DomainAnalyticsTechnologiesDomainsByLiveItem";
 export interface IDomainAnalyticsTechnologiesDomainsByTechnologyLiveResultInfo {
-    /** 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 DomainAnalyticsTechnologiesDomainsByTechnologyLiveResultInfo implements IDomainAnalyticsTechnologiesDomainsByTechnologyLiveResultInfo {
-    /** 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?: IDomainAnalyticsTechnologiesDomainsByTechnologyLiveResultInfo);

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

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

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

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

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

@@ -1,14 +1,14 @@
 export interface IDomainAnalyticsTechnologiesLanguagesResultInfo {
-    /** language name */
+    /** *language name* */
     language_name?: string | undefined;
-    /** language code according to ISO 639-1 */
+    /** *language code according to [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)* */
     language_code?: string | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesLanguagesResultInfo implements IDomainAnalyticsTechnologiesLanguagesResultInfo {
-    /** language name */
+    /** *language name* */
     language_name?: string | undefined;
-    /** language code according to ISO 639-1 */
+    /** *language code according to [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)* */
     language_code?: string | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesLanguagesResultInfo);

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

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

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

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

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

@@ -1,14 +1,14 @@
 export interface IDomainAnalyticsTechnologiesLocationsResultInfo {
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesLocationsResultInfo implements IDomainAnalyticsTechnologiesLocationsResultInfo {
-    /** full name of the location */
+    /** *full name of the location* */
     location_name?: string | undefined;
-    /** ISO country code of the location */
+    /** *ISO country code of the location* */
     country_iso_code?: string | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesLocationsResultInfo);

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

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

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

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

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

@@ -1,11 +1,11 @@
 import { Groups } from "./Groups";
 export interface IDomainAnalyticsTechnologiesTechnologiesResultInfo {
-    /** array of technology groups */
+    /** *array of technology groups* */
     groups?: Groups[] | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesTechnologiesResultInfo implements IDomainAnalyticsTechnologiesTechnologiesResultInfo {
-    /** array of technology groups */
+    /** *array of technology groups* */
     groups?: Groups[] | undefined;
     [key: string]: any;
     constructor(data?: IDomainAnalyticsTechnologiesTechnologiesResultInfo);

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

@@ -1,42 +1,42 @@
 export interface IDomainAnalyticsTechnologiesTechnologiesSummaryLiveRequestInfo {
-    /** target technology paths required field if you don’t specify groups, technologies and categories each technology path should be specified as a separate object containing “path” and “name”, where “path” is specified as “$group_id.$category_id” and “name” – as the name of the target technology; each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names on this page note: you can specify up to 10 technology paths in this array example: [{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}] */
+    /** *target technology paths* **required field if you don't specify `groups`, `technologies` and `categories`** each technology path should be specified as a separate object containing 'path' and 'name', where 'path' is specified as '$group_id.$category_id' and 'name' - as the name of the target technology;  each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology paths in this array example: `[{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}]` */
     technology_paths?: string[] | undefined;
-    /** ids of the target technology groups required field if you don’t specify technologies, technology_paths, categories, or keywords you can find the full list of technology group ids on this page note: you can specify up to 10 technology groups in this array example: ['sales', 'marketing'] */
+    /** *ids of the target technology groups* **required field if you don't specify `technologies`, `technology_paths`, `categories`, or `keywords`** you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology groups in this array example: `['sales', 'marketing']` */
     groups?: string[] | undefined;
-    /** ids of the target technology categories required field if you don’t specify groups, technology_paths, technologies, or keywords you can find the full list of technology category ids on this page note: you can specify up to 10 technology categories in this array example: ['payment_processors','crm'] */
+    /** *ids of the target technology categories* **required field if you don't specify `groups`, `technology_paths`, `technologies`, or `keywords`** you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology categories in this array example: `['payment_processors','crm']` */
     categories?: string[] | undefined;
-    /** target technologies required field if you don’t specify groups, technology_paths, categories, or keywords you can find the full list of technologies you can specify here on this page note: you can specify up to 10 technologies in this array example: ['Google Pay','Salesforce'] */
+    /** *target technologies* **required field if you don't specify `groups`, `technology_paths`, `categories`, or `keywords`** you can find the full list of technologies you can specify here [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technologies in this array example: `['Google Pay','Salesforce']` */
     technologies?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords required field if you don’t specify groups, technology_paths, categories, or technologies you can specify the maximum of 10 keywords; UTF-8 encoding; 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* **required field if you don't specify `groups`, `technology_paths`, `categories`, or `technologies`** you can specify the maximum of 10 keywords; UTF-8 encoding; 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: 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 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` 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;
-    /** maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: countries, languages, content_languages, keywords default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of elements within internal arrays* optional field you can use this field to limit the number of elements within the following arrays: `countries`, `languages`, `content_languages`, `keywords` default value: `10` minimum value: `1` maximum value: `10000` */
     internal_list_limit?: 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 DomainAnalyticsTechnologiesTechnologiesSummaryLiveRequestInfo implements IDomainAnalyticsTechnologiesTechnologiesSummaryLiveRequestInfo {
-    /** target technology paths required field if you don’t specify groups, technologies and categories each technology path should be specified as a separate object containing “path” and “name”, where “path” is specified as “$group_id.$category_id” and “name” – as the name of the target technology; each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names on this page note: you can specify up to 10 technology paths in this array example: [{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}] */
+    /** *target technology paths* **required field if you don't specify `groups`, `technologies` and `categories`** each technology path should be specified as a separate object containing 'path' and 'name', where 'path' is specified as '$group_id.$category_id' and 'name' - as the name of the target technology;  each object with a technology path should be separated with a comma you can find the full list of technology group ids, category ids and technology names [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology paths in this array example: `[{'path': 'content.cms','name': 'wordpress'}, {'path': 'marketing.crm','name': 'salesforce'}]` */
     technology_paths?: string[] | undefined;
-    /** ids of the target technology groups required field if you don’t specify technologies, technology_paths, categories, or keywords you can find the full list of technology group ids on this page note: you can specify up to 10 technology groups in this array example: ['sales', 'marketing'] */
+    /** *ids of the target technology groups* **required field if you don't specify `technologies`, `technology_paths`, `categories`, or `keywords`** you can find the full list of technology group ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology groups in this array example: `['sales', 'marketing']` */
     groups?: string[] | undefined;
-    /** ids of the target technology categories required field if you don’t specify groups, technology_paths, technologies, or keywords you can find the full list of technology category ids on this page note: you can specify up to 10 technology categories in this array example: ['payment_processors','crm'] */
+    /** *ids of the target technology categories* **required field if you don't specify `groups`, `technology_paths`, `technologies`, or `keywords`** you can find the full list of technology category ids [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technology categories in this array example: `['payment_processors','crm']` */
     categories?: string[] | undefined;
-    /** target technologies required field if you don’t specify groups, technology_paths, categories, or keywords you can find the full list of technologies you can specify here on this page note: you can specify up to 10 technologies in this array example: ['Google Pay','Salesforce'] */
+    /** *target technologies* **required field if you don't specify `groups`, `technology_paths`, `categories`, or `keywords`** you can find the full list of technologies you can specify here [on this page](/v3/domain_analytics/technologies/technologies) **note:** you can specify up to 10 technologies in this array example: `['Google Pay','Salesforce']` */
     technologies?: string[] | undefined;
-    /** target keywords in the domain’s title, description or meta keywords required field if you don’t specify groups, technology_paths, categories, or technologies you can specify the maximum of 10 keywords; UTF-8 encoding; 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* **required field if you don't specify `groups`, `technology_paths`, `categories`, or `technologies`** you can specify the maximum of 10 keywords; UTF-8 encoding; 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: 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 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` 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;
-    /** maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: countries, languages, content_languages, keywords default value: 10 minimum value: 1 maximum value: 10000 */
+    /** *maximum number of elements within internal arrays* optional field you can use this field to limit the number of elements within the following arrays: `countries`, `languages`, `content_languages`, `keywords` default value: `10` minimum value: `1` maximum value: `10000` */
     internal_list_limit?: 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?: IDomainAnalyticsTechnologiesTechnologiesSummaryLiveRequestInfo);

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

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

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

@@ -1,36 +1,36 @@
 export interface IDomainAnalyticsTechnologiesTechnologiesSummaryLiveResultInfo {
-    /** distribution of websites by country contains country codes and number of websites per country */
+    /** *distribution of websites by country* contains country codes and number of websites per country */
     countries?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by language contains language codes and number of websites per language */
+    /** *distribution of websites by language* contains language codes and number of websites per language */
     languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by content language contains content language codes and number of websites per language */
+    /** *distribution of websites by content language* contains content language codes and number of websites per language */
     content_languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by keywords contains keywords found in the websites’ titles, descriptions or meta keywords, and number of websites using each keyword */
+    /** *distribution of websites by keywords* contains keywords found in the websites' titles, descriptions or meta keywords, and number of websites using each keyword */
     keywords?: {
         [key: string]: number;
     } | undefined;
     [key: string]: any;
 }
 export declare class DomainAnalyticsTechnologiesTechnologiesSummaryLiveResultInfo implements IDomainAnalyticsTechnologiesTechnologiesSummaryLiveResultInfo {
-    /** distribution of websites by country contains country codes and number of websites per country */
+    /** *distribution of websites by country* contains country codes and number of websites per country */
     countries?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by language contains language codes and number of websites per language */
+    /** *distribution of websites by language* contains language codes and number of websites per language */
     languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by content language contains content language codes and number of websites per language */
+    /** *distribution of websites by content language* contains content language codes and number of websites per language */
     content_languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by keywords contains keywords found in the websites’ titles, descriptions or meta keywords, and number of websites using each keyword */
+    /** *distribution of websites by keywords* contains keywords found in the websites' titles, descriptions or meta keywords, and number of websites using each keyword */
     keywords?: {
         [key: string]: number;
     } | undefined;

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

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

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

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

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

@@ -1,19 +1,19 @@
 export interface IDomainAnalyticsTechnologiesTechnologyStatsLiveItem {
     /** type of element */
     type?: string | undefined;
-    /** date for which the data is provided */
+    /** *date for which the data is provided* */
     date?: string | undefined;
-    /** number of domains that use the specified technology */
+    /** *number of domains that use the specified technology* */
     domains_count?: number | undefined;
-    /** distribution of websites by country contains country codes and number of websites per country */
+    /** *distribution of websites by country* contains country codes and number of websites per country */
     countries?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by language contains language codes and number of websites per language */
+    /** *distribution of websites by language* contains language codes and number of websites per language */
     languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by backlink rank contains domain rank ranges and number of websites per range learn more about rank and how it is calculated in this help center article */
+    /** *distribution of websites by backlink rank* contains domain rank ranges and number of websites per range learn more about rank and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domains_rank?: {
         [key: string]: number;
     } | undefined;
@@ -22,19 +22,19 @@ export interface IDomainAnalyticsTechnologiesTechnologyStatsLiveItem {
 export declare class DomainAnalyticsTechnologiesTechnologyStatsLiveItem implements IDomainAnalyticsTechnologiesTechnologyStatsLiveItem {
     /** type of element */
     type?: string | undefined;
-    /** date for which the data is provided */
+    /** *date for which the data is provided* */
     date?: string | undefined;
-    /** number of domains that use the specified technology */
+    /** *number of domains that use the specified technology* */
     domains_count?: number | undefined;
-    /** distribution of websites by country contains country codes and number of websites per country */
+    /** *distribution of websites by country* contains country codes and number of websites per country */
     countries?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by language contains language codes and number of websites per language */
+    /** *distribution of websites by language* contains language codes and number of websites per language */
     languages?: {
         [key: string]: number;
     } | undefined;
-    /** distribution of websites by backlink rank contains domain rank ranges and number of websites per range learn more about rank and how it is calculated in this help center article */
+    /** *distribution of websites by backlink rank* contains domain rank ranges and number of websites per range learn more about rank and how it is calculated in [this help center article](https://dataforseo.com/help-center/what_is_rank_in_backlinks_api) */
     domains_rank?: {
         [key: string]: number;
     } | undefined;