> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Dataforseo Domain Analytics Technologies Domains By Html
> This endpoint provides domains based on the HTML terms they use on their homepage. Includes inputs, outputs, costs, and Deepline CLI examples.
## Run in Enrichment Spreadsheet
Use this function as a column step in `deepline enrich`.
```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=dataforseo_domain_analytics_technologies_domains_by_html_terms_live:{"search_terms":"{{search_terms}}"}' --json
```
Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
## Input Schema
| Name | Type | Required | Default | Description |
| ---------------------- | --------- | -------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `payload.search_terms` | `array` | Yes | | 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"] |
| `payload.keywords` | `array` | No | | 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 |
| `payload.mode` | `string` | No | | 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 |
| `payload.filters` | `array` | No | | 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 |
| `payload.order_by` | `array` | No | | 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"] |
| `payload.limit` | `integer` | No | | the maximum number of returned domains optional field default value: 100 maximum value: 10000 |
| `payload.offset` | `integer` | No | | 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 |
| `payload.offset_token` | `string` | No | | 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 |
Show raw input schema
### Input JSON Schema
```json theme={null}
{
"type": "object",
"description": "This endpoint provides domains based on the HTML terms they use on their homepage. In addition to the list of domains, you will also get their technology profiles, the country and language they belong to, and other related data.",
"properties": {
"search_terms": {
"type": "array",
"description": "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\"]",
"items": {}
},
"keywords": {
"type": "array",
"description": "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",
"items": {}
},
"mode": {
"type": "string",
"description": "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"
},
"filters": {
"type": "array",
"description": "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",
"items": {}
},
"order_by": {
"type": "array",
"description": "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\"]",
"items": {}
},
"limit": {
"type": "integer",
"description": "the maximum number of returned domains optional field default value: 100 maximum value: 10000"
},
"offset": {
"type": "integer",
"description": "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_token": {
"type": "string",
"description": "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"
}
},
"required": [
"search_terms"
],
"additionalProperties": false
}
```
## Output Schema
| Name | Type | Required | Default | Description |
| ----------------------- | --------- | -------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `result.version` | `string` | Yes | | the current version of the API |
| `result.status_code` | `integer` | Yes | | general status code you can find the full list of the response codes here Note: we strongly recommend designing a necessary system for handling related exceptional or error conditions |
| `result.status_message` | `string` | Yes | | general informational message you can find the full list of general informational messages here |
| `result.time` | `string` | Yes | | execution time, seconds |
| `result.tasks_count` | `integer` | Yes | | the number of tasks in the tasks array |
| `result.tasks_error` | `integer` | Yes | | the number of tasks in the tasks array returned with an error |
| `result.tasks` | `array` | Yes | | array of tasks |
Show raw output schema
### Output JSON Schema
```json theme={null}
{
"type": "object",
"description": "Top-level response envelope for dataforseo_domain_analytics_technologies_domains_by_html_terms_live.",
"properties": {
"version": {
"type": "string",
"description": "the current version of the API"
},
"status_code": {
"type": "integer",
"description": "general status code you can find the full list of the response codes here Note: we strongly recommend designing a necessary system for handling related exceptional or error conditions"
},
"status_message": {
"type": "string",
"description": "general informational message you can find the full list of general informational messages here"
},
"time": {
"type": "string",
"description": "execution time, seconds"
},
"tasks_count": {
"type": "integer",
"description": "the number of tasks in the tasks array"
},
"tasks_error": {
"type": "integer",
"description": "the number of tasks in the tasks array returned with an error"
},
"tasks": {
"type": "array",
"description": "array of tasks",
"items": {}
}
},
"required": [
"version",
"status_code",
"status_message",
"time",
"tasks_count",
"tasks_error",
"tasks"
],
"additionalProperties": false
}
```
## Advanced: Direct CLI
Use direct execution for single payload debugging.
```bash theme={null}
deepline tools execute dataforseo_domain_analytics_technologies_domains_by_html_terms_live --payload '{
"search_terms": "array"
}' --json
```
### CLI flags
| Flag | Description |
| --------------------------- | --------------------------------------------------- |
| `--json` | Print machine-readable output. |
| `--wait` | Wait for terminal provider status when supported. |
| `--debug` | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS` | Max seconds to wait in wait mode. |
| `--poll-interval SECONDS` | Polling interval in seconds during wait mode. |
| `--timeout SECONDS` | Request timeout in seconds. |
| `--connect-timeout SECONDS` | Connection timeout in seconds. |
## Cost
* Pricing model: `provider_usage` (provider usage).
* Estimated Deepline credits: `0.02` per pricing unit.
* Billing mode: `post_deduct`.