DataForSEO: Domain Analytics Technologies Domains By Technology Live

Find domains that use a given technology.

Tool ID: dataforseo_domain_analytics_technologies_domains_by_technology_live

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'dataforseo_domain_analytics_technologies_domains_by_technology_live',
  {
    "technology_paths": [
      {}
    ],
    "groups": [
      {}
    ],
    "categories": [
      {}
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute dataforseo_domain_analytics_technologies_domains_by_technology_live --input '{
  "technology_paths": [
    {}
  ],
  "groups": [
    {}
  ],
  "categories": [
    {}
  ]
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "version": "example",
  "status_code": 123,
  "status_message": "example",
  "time": "example",
  "tasks_count": 123,
  "tasks_error": 123,
  "tasks": [
    {}
  ]
}

Use deepline describe dataforseo_domain_analytics_technologies_domains_by_technology_live --json for the latest machine-readable contract.

Input reference

This endpoint provides domains based on the technology they use. 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.

Name	Type	Required	Default	Details
`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 “ $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 See the live schema for the complete constraint.
`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], See the live schema for the complete constraint.
`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 See the live schema for the complete constraint.
`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 See the live schema for the complete constraint.

Output reference

Top-level response envelope for dataforseo_domain_analytics_technologies_domains_by_technology_live.

Name	Type	Required	Default	Details
`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

Deepline cost

Pricing model: provider_usage (provider usage).
Estimated Deepline credits: 0.02 per pricing unit.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation