DataForSEO: Domain Analytics Technologies Aggregation Technologies Live

Find the technologies websites most often use alongside the technologies, groups or categories you name.

Tool ID: dataforseo_domain_analytics_technologies_aggregation_technologies_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_aggregation_technologies_live',
  {
    "group": "example",
    "category": "example",
    "technology": "example"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute dataforseo_domain_analytics_technologies_aggregation_technologies_live --input '{
  "group": "example",
  "category": "example",
  "technology": "example"
}' --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_aggregation_technologies_live --json for the latest machine-readable contract.

Input reference

The Aggregation Technologies endpoint will provide you with a list of the most popular technologies websites use alongside the technologies you specify. Alternatively, you can specify technology categories or groups to obtain wider stats.

Name	Type	Required	Default	Details
`payload.group`	`string`	No	—	id of the target technology group required field if you don’t specify technology , category or keyword at least one field ( group , category , keyword , technology ) must be set you can find the full list of technology group ids on this page example: “marketing”
`payload.category`	`string`	No	—	id of the target technology category required field if you don’t specify group , keyword or technology at least one field ( group , category , keyword , technology ) must be set you can find the full list of technology category ids on this page example: “crm”
`payload.technology`	`string`	No	—	target technology required field if you don’t specify group , keyword or category at least one field ( group , category , keyword , technology ) must be set you can find the full list of technologies on this page example: “Salesforce”
`payload.keyword`	`string`	No	—	target keyword in the domain’s meta keywords required field if you don’t specify group , category or technology at least one field ( group , category , keyword , technology ) must be set UTF-8 encoding example: “seo” 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 , See the live schema for the complete constraint.
`payload.order_by`	`array`	No	—	results sorting rules optional field you can use the following values to sort the results: groups_count , categories_count , technologies_count 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: [“groups_count,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: See the live schema for the complete constraint.
`payload.internal_groups_list_limit`	`integer`	No	—	maximum number of returned technology groups optional field you can use this field to limit the number of items with identical “group” in the results default value: 5 minimum value: 1 maximum value: 10000
`payload.internal_categories_list_limit`	`integer`	No	—	maximum number of returned technology categories within the same group optional field you can use this field to limit the number of items with identical “category” in the results default value: 5 minimum value: 1 maximum value: 10000
`payload.internal_technologies_list_limit`	`integer`	No	—	maximum number of returned technologies within the same category optional field you can use this field to limit the number of items with identical “technology” in the results default value: 10 minimum value: 1 maximum value: 10000
`payload.internal_list_limit`	`integer`	No	—	maximum number of items with identical “category” , “group” , and “technology” optional field if you use this field, the values specified in internal_groups_list_limit , internal_categories_list_limit and internal_technologies_list_limit will be ignored. You can use this field to limit the number of items with identical “category” , “group” , or “technology” default value: 10 minimum value: 1 maximum value: 10000
`payload.limit`	`integer`	No	—	the maximum number of returned technologies 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 maximum value: 9999 if you specify the 10 value, the first ten technologies in the results array will be omitted and the data will be provided for the successive technologies
`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

Output reference

Top-level response envelope for dataforseo_domain_analytics_technologies_aggregation_technologies_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