Reference example
# Fixed reference example. Playground inputs do not update this sample.
curl --request POST \
--url https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '[
{
"mode": "entry",
"technologies": [
"Ngi"
],
"keywords": [
"WordPress"
],
"filters": [
[
"country_iso_code",
"=",
"US"
],
"and",
[
"domain_rank",
">",
800
]
]
}
]'curl --request POST \
--url https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
[
{
"filters": [
[
"country_iso_code",
"=",
"US"
],
"and",
[
"domain_rank",
">",
800
]
],
"keywords": [
"WordPress"
],
"mode": "entry",
"technologies": [
"Ngi"
]
}
]
'import requests
url = "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live"
payload = [
{
"filters": [["country_iso_code", "=", "US"], "and", ["domain_rank", ">", 800]],
"keywords": ["WordPress"],
"mode": "entry",
"technologies": ["Ngi"]
}
]
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify([
{
filters: [['country_iso_code', '=', 'US'], 'and', ['domain_rank', '>', 800]],
keywords: ['WordPress'],
mode: 'entry',
technologies: ['Ngi']
}
])
};
fetch('https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
[
'filters' => [
[
'country_iso_code',
'=',
'US'
],
'and',
[
'domain_rank',
'>',
800
]
],
'keywords' => [
'WordPress'
],
'mode' => 'entry',
'technologies' => [
'Ngi'
]
]
]),
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>",
"Content-Type: application/json"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live"
payload := strings.NewReader("[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("Authorization", "Bearer <token>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live")
.header("Authorization", "Bearer <token>")
.header("Content-Type", "application/json")
.body("[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]"
response = http.request(request)
puts response.read_body{
"cost": 123,
"status_code": 123,
"status_message": "<string>",
"tasks_count": 123,
"tasks_error": 123,
"time": "<string>",
"version": "<string>",
"tasks": [
{
"cost": 123,
"data": {},
"id": "<string>",
"path": [
"<string>"
],
"result_count": 123,
"status_code": 123,
"status_message": "<string>",
"time": "<string>",
"result": [
{
"content_languages": {},
"countries": {},
"keywords": {},
"languages": {}
}
]
}
]
}Domain Analytics
Technologies Summary
Where a technology is used, rather than by whom: returns countries, languages, content_languages and keywords for the technology set you name.
POST
https://api.aisa.one
/
apis
/
v1
/
dataforseo
/
domain_analytics
/
technologies
/
technologies_summary
/
live
Reference example
# Fixed reference example. Playground inputs do not update this sample.
curl --request POST \
--url https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '[
{
"mode": "entry",
"technologies": [
"Ngi"
],
"keywords": [
"WordPress"
],
"filters": [
[
"country_iso_code",
"=",
"US"
],
"and",
[
"domain_rank",
">",
800
]
]
}
]'curl --request POST \
--url https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
[
{
"filters": [
[
"country_iso_code",
"=",
"US"
],
"and",
[
"domain_rank",
">",
800
]
],
"keywords": [
"WordPress"
],
"mode": "entry",
"technologies": [
"Ngi"
]
}
]
'import requests
url = "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live"
payload = [
{
"filters": [["country_iso_code", "=", "US"], "and", ["domain_rank", ">", 800]],
"keywords": ["WordPress"],
"mode": "entry",
"technologies": ["Ngi"]
}
]
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify([
{
filters: [['country_iso_code', '=', 'US'], 'and', ['domain_rank', '>', 800]],
keywords: ['WordPress'],
mode: 'entry',
technologies: ['Ngi']
}
])
};
fetch('https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
[
'filters' => [
[
'country_iso_code',
'=',
'US'
],
'and',
[
'domain_rank',
'>',
800
]
],
'keywords' => [
'WordPress'
],
'mode' => 'entry',
'technologies' => [
'Ngi'
]
]
]),
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>",
"Content-Type: application/json"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live"
payload := strings.NewReader("[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("Authorization", "Bearer <token>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live")
.header("Authorization", "Bearer <token>")
.header("Content-Type", "application/json")
.body("[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "[\n {\n \"filters\": [\n [\n \"country_iso_code\",\n \"=\",\n \"US\"\n ],\n \"and\",\n [\n \"domain_rank\",\n \">\",\n 800\n ]\n ],\n \"keywords\": [\n \"WordPress\"\n ],\n \"mode\": \"entry\",\n \"technologies\": [\n \"Ngi\"\n ]\n }\n]"
response = http.request(request)
puts response.read_body{
"cost": 123,
"status_code": 123,
"status_message": "<string>",
"tasks_count": 123,
"tasks_error": 123,
"time": "<string>",
"version": "<string>",
"tasks": [
{
"cost": 123,
"data": {},
"id": "<string>",
"path": [
"<string>"
],
"result_count": 123,
"status_code": 123,
"status_message": "<string>",
"time": "<string>",
"result": [
{
"content_languages": {},
"countries": {},
"keywords": {},
"languages": {}
}
]
}
]
}Where a technology is used, rather than by whom: returns
Set this endpoint up in your agent →
countries, languages, content_languages and keywords for the technology set you name. Measured at 1.4 KB. Wrapped in DataForSEO’s envelope: data in tasks[0].result, and the real outcome in tasks[0].status_code - a rejected request still returns HTTP 200, so check that field rather than the transport status. Use it to size a market before pulling domain lists. For counts broken down by group and category use post_dataforseo_domains_tech_aggregation_live; for adoption over time, post_dataforseo_domains_tech_technology_stats_live.
Example
curl -X POST "https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '[{"technology_paths": "...", "groups": "...", "categories": "..."}]'
// Copy this whole block into Claude Code, Codex, Cursor or any coding agent.
// It carries everything needed to connect, authorize and run this example —
// no key to paste, one click of Allow in the browser.
{
"calls": [
{
"call_id": "1",
"tool": "post_dataforseo_domains_tech_summary_live",
"arguments": {}
}
]
}
// ── for the agent ─────────────────────────────────────────────────────────
// Register the AIsa MCP server, then call its `batch_quote` tool with the JSON above.
// name aisa
// endpoint https://mcp.aisa.one/mcp
// transport streamable-http
// auth OAuth. The server publishes RFC 9728 metadata, so open a
// browser and the user clicks Allow once — nothing to paste.
// If AISA_API_KEY is set, send it as a bearer header instead.
// Use your own MCP mechanism, not a hand-edited config file:
// Codex codex mcp add aisa --url https://mcp.aisa.one/mcp
// Claude Code claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp
// Cursor / VS Code a "url" entry for https://mcp.aisa.one/mcp in the MCP config
// The server reaches https://mcp.aisa.one/servers worth of APIs through a few meta
// tools: search, list_categories, get_details, batch_quote, batch_use.
// search, get_details and batch_quote are free; batch_use is billed per
// call. This operation's full contract — every argument, the response
// shape, the price and the pitfalls — is at
// https://aisa.one/docs/api-reference/dataforseo/post_dataforseo-domain-analytics-technologies-technologies-summary-live.md
// Show me the quoted cost. Once I approve, run the same calls with
// batch_use and show me the result.
First time? Point any MCP client at
https://mcp.aisa.one/mcp — Claude
Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client
opens a browser, you click Allow once, and there is no key to paste. Your
agent then reaches every endpoint through a few meta tools: search,
list_categories, get_details and batch_quote are free, batch_use is
billed per call. Setup per client is in
Connect via MCP; the live tool list and what each call
costs are on aisa.one/mcp.Request contract
- Method and path: POST /apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live
- Availability: enabled
- Request URL template: https://api.aisa.one/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live
- Runtime facts: 6ab8fec17df1d5dcdff2e036dd1eb40587752b774ec040ab4eb0cc6946c3dd3c
{
"operationId": "post_dataforseo_domains_tech_summary_live",
"method": "POST",
"path": "/apis/v1/dataforseo/domain_analytics/technologies/technologies_summary/live",
"servers": [
{
"url": "https://api.aisa.one"
}
],
"parameters": [],
"security": [
{
"bearerAuth": []
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"example": [
{
"filters": [
[
"country_iso_code",
"=",
"US"
],
"and",
[
"domain_rank",
">",
800
]
],
"keywords": [
"WordPress"
],
"mode": "entry",
"technologies": [
"Ngi"
]
}
],
"items": {
"oneOf": [
{
"properties": {
"categories": {
"description": "<em>ids of the target technology categories</em><br><strong>required field if you don't specify <code>groups</code>, <code>technology_paths</code>, <code>technologies</code>, or <code>keywords</code></strong><br>you can find the full list of technology category ids <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br><strong>note:</strong> you can specify up to 10 technology categories in this array<br>example:<br><code>[\"payment_processors\",\"crm\"]</code>",
"items": {
"type": "string"
},
"type": "array"
},
"filters": {
"description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code><</code>, <code><=</code>, <code>></code>, <code>>=</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>,<code>not_like</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>you can use the following parameters to filter the results: <code>domain_rank</code>, <code>last_visited</code>, <code>country_iso_code</code>, <code>language_code</code>, <code>content_language_code</code><br>example:<br><code>[[\"country_iso_code\",\"=\",\"US\"],<br>\"and\",<br>[\"domain_rank\",\">\",800]]</code><p>for more information about filters, please refer to <a href=\"/v3/domain_analytics/technologies/filters\" target=\"_blank\" rel=\"noopener noreferrer\">Domain Analytics Technologies API - Filters</a>",
"items": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"additionalProperties": {
"$ref": "#/components/schemas/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
},
"type": [
"object",
"null"
]
},
{
"items": {
"$ref": "#/components/schemas/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
},
"type": "array"
}
],
"description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator."
},
"type": [
"array",
"null"
]
},
"groups": {
"description": "<em>ids of the target technology groups</em><br><strong>required field if you don't specify <code>technologies</code>, <code>technology_paths</code>, <code>categories</code>, or <code>keywords</code></strong><br>you can find the full list of technology group ids <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br><strong>note:</strong> you can specify up to 10 technology groups in this array<br>example:<br><code>[\"sales\", \"marketing\"]</code>",
"items": {
"type": "string"
},
"type": "array"
},
"internal_list_limit": {
"description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>countries</code>, <code>languages</code>, <code>content_languages</code>, <code>keywords</code><br>default value: <code>10</code><br>minimum value: <code>1</code><br>maximum value: <code>10000</code>",
"type": [
"integer",
"null"
]
},
"keywords": {
"description": "<em>target keywords in the domain's title, description or meta keywords</em><br><strong>required field if you don't specify <code>groups</code>, <code>technology_paths</code>, <code>categories</code>, or <code>technologies</code></strong><br>you can specify the maximum of 10 keywords;<br>UTF-8 encoding;<br>example:<br><code>[\"seo\",\"software\"]</code><p>learn more about rules and limitations of <code>keyword</code> and <code>keywords</code> fields in DataForSEO APIs in this <a href=\"https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis\" rel=\"noopener noreferrer\" target=\"_blank\">Help Center article</a>",
"items": {
"type": "string"
},
"type": "array"
},
"mode": {
"description": "<em>search mode</em><br>optional field<br>possible search mode types:<br><code>as_is</code> - search for results exactly matching the specified group ids, category ids, or technology names<br><code>entry</code> - search for results matching a part of the specified group ids, category ids, or technology names<br>default value: <code>as_is</code>",
"type": [
"string",
"null"
]
},
"tag": {
"description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response",
"type": [
"string",
"null"
]
},
"technologies": {
"description": "<em>target technologies</em><br><strong>required field if you don't specify <code>groups</code>, <code>technology_paths</code>, <code>categories</code>, or <code>keywords</code></strong><br>you can find the full list of technologies you can specify here <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br><strong>note:</strong> you can specify up to 10 technologies in this array<br>example:<br><code>[\"Google Pay\",\"Salesforce\"]</code>",
"items": {
"type": "string"
},
"type": "array"
},
"technology_paths": {
"description": "<em>target technology paths</em><br><strong>required field if you don't specify <code>groups</code>, <code>technologies</code> and <code>categories</code></strong><br>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; <br>each object with a technology path should be separated with a comma<br>you can find the full list of technology group ids, category ids and technology names <a href=\"/v3/domain_analytics/technologies/technologies\" target=\"_blank\" rel=\"noopener noreferrer\">on this page</a><br><strong>note:</strong> you can specify up to 10 technology paths in this array<br>example:<br><code>[{\"path\": \"content.cms\",\"name\": \"wordpress\"}, {\"path\": \"marketing.crm\",\"name\": \"salesforce\"}]</code>",
"items": {
"type": "string"
},
"type": "array"
}
},
"type": "object"
}
],
"type": [
"object",
"null"
]
},
"type": "array"
}
}
}
},
"x-aisa-status": "enabled",
"x-aisa-pricing": {
"cost_contract": "response_usd",
"customer_multiplier": 1.0,
"customer_pricing": "provider_cost_multiplier",
"default_request_estimate_usd": 0.012,
"estimate_source": "profile_seed",
"evidence_source": "response_body"
},
"components": {
"schemas": {
"Provider0A3E90081762_AisaDataforseoFilterJsonValue": {
"anyOf": [
{
"type": "string"
},
{
"type": "number"
},
{
"type": "boolean"
},
{
"additionalProperties": {
"$ref": "#/components/schemas/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
},
"type": [
"object",
"null"
]
},
{
"items": {
"$ref": "#/components/schemas/Provider0A3E90081762_AisaDataforseoFilterJsonValue"
},
"type": "array"
}
],
"description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator."
}
},
"securitySchemes": {
"bearerAuth": {
"scheme": "bearer",
"type": "http"
}
}
}
}
Cost and request rules
Usage-based billing; Default request estimate: $0.012 USD (not a fixed price). Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.- Default request reference estimate (USD): 0.012
- Cost contract: response_usd
- Published reference multiplier: 1.0
- Settlement evidence source: response_body
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
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"]
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
JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator.
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"]
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
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
search mode
optional field
possible search mode types:as_is - search for results exactly matching the specified group ids, category ids, or technology namesentry - search for results matching a part of the specified group ids, category ids, or technology names
default value: as_is
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
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"]
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"}]
Example:
[
{
"filters": [
["country_iso_code", "=", "US"],
"and",
["domain_rank", ">", 800]
],
"keywords": ["WordPress"],
"mode": "entry",
"technologies": ["Ngi"]
}
]
Response
object | null
Successful operation
total tasks cost, USD
general status code you can find the full list of the response codes here
general informational message you can find the full list of general informational messages here
the number of tasks in the tasks array
the number of tasks in the tasks array returned with an error
total execution time, seconds
the current version of the API
array of tasks
Show child attributes
Show child attributes