> ## 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 Technologies
> The Technologies Summary endpoint will provide you with the number of domains across different countries and languages that use the specified technology names
## 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_technologies_summary_live:{}' --json
```
Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
## Input Schema
| Name | Type | Required | Default | Description |
| ----------------------------- | --------- | -------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `payload.technology_paths` | `array` | No | | 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"}] |
| `payload.groups` | `array` | No | | 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"] |
| `payload.categories` | `array` | No | | 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"] |
| `payload.technologies` | `array` | No | | 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"] |
| `payload.keywords` | `array` | No | | 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 |
| `payload.mode` | `string` | No | | 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 |
| `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 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 |
| `payload.internal_list_limit` | `integer` | No | | 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 |
| `payload.tag` | `string` | No | | 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 |
Show raw input schema
### Input JSON Schema
```json theme={null}
{
"type": "object",
"description": "The Technologies Summary endpoint will provide you with the number of domains across different countries and languages that use the specified technology names, technology groups, or technology categories.",
"properties": {
"technology_paths": {
"type": "array",
"description": "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\"}]",
"items": {}
},
"groups": {
"type": "array",
"description": "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\"]",
"items": {}
},
"categories": {
"type": "array",
"description": "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\"]",
"items": {}
},
"technologies": {
"type": "array",
"description": "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\"]",
"items": {}
},
"keywords": {
"type": "array",
"description": "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",
"items": {}
},
"mode": {
"type": "string",
"description": "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"
},
"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 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",
"items": {}
},
"internal_list_limit": {
"type": "integer",
"description": "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"
},
"tag": {
"type": "string",
"description": "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"
}
},
"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_technologies_summary_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_technologies_summary_live --payload '{}' --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`.