Run in Enrichment Spreadsheet
Use this function as a column step in
deepline enrich.deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=dataforseo_domain_analytics_technologies_domains_by_technology_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 , 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 “groupid.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 , 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”] | |
payload.categories | array | No | 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”] | |
payload.technologies | array | No | 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”] | |
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 , 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 | |
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 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 | |
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 |
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 |
Advanced: Direct CLI
Use direct execution for single payload debugging.
deepline tools execute dataforseo_domain_analytics_technologies_domains_by_technology_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.02per pricing unit. - Billing mode:
post_deduct.