Technologies Domains By Technology
dataforseo/technologies_domains_by_technology_liveRun a technologies domains by technology report.
- call
- Price: —
- DataForSEO
- 3 min
Overview
Runs the technologies domains by technology operation and returns the structured result from the data provider.
Structured report results and task status.
Input
These go in the input object of the run request.
| Field | Type | Required | Description |
|---|---|---|---|
| technology_paths | array | No | Technology path objects with path ($group_id.$category_id) and name. Supply at least one of technology_paths, groups, categories, technologies, or keywords. |
| groups | array | No | Ids of the target technology groups. Required if you don't specify technologies, technology_paths, keywords or categories. |
| categories | array | No | Ids of the target technology categories. Required if you don't specify groups, technology_paths, keywords or technologies. |
| technologies | array | No | Target technologies. Required if you don't specify groups, technology_paths, keywords or categories. |
| keywords | array | No | Target keywords in the domain's title, description or meta keywords. Required if you don't specify groups, technology_paths, technologies or categories. |
Requests up to 1 MB.
Example
Use your own API key and a saved idempotency key for each new job. Replace image or media placeholders with your own publicly reachable HTTPS URLs. Keep the same key and request body when recovering a timeout.
# Set once per job; reuse this key and the identical body after a timeout.
: "${AGENTSKY_IDEMPOTENCY_KEY:?Set a unique, saved key for this job}"
curl --fail-with-body https://gateway.agentsky.dev/v1/run \
-H "authorization: Bearer $AGENTSKY_API_KEY" \
-H "content-type: application/json" \
-H "Idempotency-Key: $AGENTSKY_IDEMPOTENCY_KEY" \
-d '{"provider":"dataforseo","endpoint":"technologies_domains_by_technology_live","input":{"technologies":["Nginx"]}}'
# If status is READY/RUNNING, poll GET /v1/runs/{runId} with the same API key.Pricing
— per call using your plan when signed in. Read the final customer charge from price.amount.value after the run finishes. A RUNNING response is not the final bill.
