Data API / DataForSEO / Domain Analytics
Domain Whois Overview
Whois records enriched with SEO metrics. Each item carries domain, created_datetime, changed_datetime, expiration_datetime, updated_datetime, first_seen, epp_status_codes, tld, registered, registrar, plus metrics and backlinks_info. Paged with limit, offset and offset_token, filtered over the fields in get_dataforseo_domains_whois_available_filters.
Параметры
Параметров пути, запроса и заголовков нет.
Тело запроса
limitintegerНеобязательныйthe maximum number of returned domains optional field default value: 100 maximum value: 1000
offsetintegerНеобязательныйoffset in the results array of returned items optional field default value: 0 if you specify the 10 value, the first ten items in the results array will be omitted and the data will be provided for the successive items; Note: we recommend using this parameter only when retrieving up to 10,000 results for retrieving over 10,000 results, use the offset_token instead
offset_tokenstringНеобязательный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
filtersarrayНеобязательный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: regex, , , >, >=, =, , 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
order_bystring[]Необязательныйresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc - results will be sorted in the ascending order desc - results will be sorted in the descending order the comma is used as a separator example: ["metrics.organic.pos_1,desc"] default rule: ["metrics.organic.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: ["expiration_datetime,asc","metrics.organic.etv,desc","metrics.organic.pos_1,desc"]
tagstringНеобязательный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
Пример запроса
curl -X POST "https://openapi.felo.ai/v1/beta/dataforseo/domain_analytics/whois/overview/live" \
-H "Authorization: Bearer $FELO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"limit": 0,
"offset": 0,
"offset_token": "<string>",
"filters": "<string>",
"order_by": [
"<string>"
],
"tag": "<string>"
}'Ответ
Поля ответа
versionstringНеобязательныйthe current version of the API
status_codeintegerНеобязательный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
status_messagestringНеобязательныйgeneral informational message you can find the full list of general informational messages here
timestringНеобязательныйexecution time, seconds
costnumberНеобязательныйtotal tasks cost, USD
tasks_countintegerНеобязательныйthe number of tasks in the tasks array
tasks_errorintegerНеобязательныйthe number of tasks in the tasks array returned with an error
tasksstring[]Необязательныйarray of tasks
idstringНеобязательныйtask identifier unique task identifier in our system in the UUID format
status_codeintegerНеобязательныйstatus code of the task generated by DataForSEO; can be within the following range: 10000-60000 you can find the full list of the response codes here
status_messagestringНеобязательныйinformational message of the task you can find the full list of general informational messages here
timestringНеобязательныйexecution time, seconds
costnumberНеобязательныйcost of the task, USD
result_countintegerНеобязательныйnumber of elements in the result array
pathstring[]НеобязательныйURL path
dataobjectНеобязательныйcontains the same parameters that you specified in the POST request
resultstring[]Необязательныйarray of results
total_countintegerНеобязательныйtotal amount of results in our database relevant to your request
items_countintegerНеобязательныйthe number of results returned in the items array
offsetintegerНеобязательныйresults offset value specified in POST request
offset_tokenobjectНеобязательныйtoken for subsequent requests by specifying the unique offset_token when setting a new task, you will get the subsequent results of the initial task; offset_token values are unique for each subsequent task
itemsstring[]Необязательныйcontains ranking and traffic data
domainstringНеобязательныйdomain name
created_datetimestringНеобязательныйdate and time of registration date and time (in the ISO 8601 format) when the domain was first registered example: "1997-03-29 03:00:00 +00:00"
changed_datetimestringНеобязательныйdate and time when the domain entry was changed date and time (in the ISO 8601 format) when the domain entry was last modified example: "2021-01-14 08:36:28 +00:00"
expiration_datetimestringНеобязательныйdate and time when the domain will expire date and time (in the ISO 8601 format) when the domain is due to expire example: "2022-11-26 17:21:23 +00:00"
updated_datetimestringНеобязательныйdate and time when the domain was updated date and time (in the ISO 8601 format) when the domain was last updated example: "2021-01-29 13:59:38 +00:00"
first_seenstringНеобязательныйdate and time when our crawler found the domain for the first time in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: "2019-11-15 12:57:46 +00:00"
epp_status_codesstring[]Необязательныйextensive provisioning protocol status codes the status of a domain name registration as defined by ICANN
tldstringНеобязательныйtop-level domain top-level domain in the DNS root zone
registeredbooleanНеобязательныйdomain registration status if false, the domain name registration has expired Note: expired domains will remain in the database for only a short period of time
registrarstringНеобязательныйdomain registrar if null, the domain registrar is unknown example: NameCheap, Inc.
metricsobjectНеобязательныйranking data relevant to the specified domain
organicobjectНеобязательныйranking and traffic data from organic search
pos_1integerНеобязательныйnumber of organic SERPs where the domain ranks #1
pos_2_3integerНеобязательныйnumber of organic SERPs where the domain ranks #2-3
pos_4_10integerНеобязательныйnumber of organic SERPs where the domain ranks #4-10
pos_11_20integerНеобязательныйnumber of organic SERPs where the domain ranks #11-20
pos_21_30integerНеобязательныйnumber of organic SERPs where the domain ranks #21-30
pos_31_40integerНеобязательныйnumber of organic SERPs where the domain ranks #31-40
pos_41_50integerНеобязательныйnumber of organic SERPs where the domain ranks #41-50
pos_51_60integerНеобязательныйnumber of organic SERPs where the domain ranks #51-60
pos_61_70integerНеобязательныйnumber of organic SERPs where the domain ranks #61-70
pos_71_80integerНеобязательныйnumber of organic SERPs where the domain ranks #71-80
pos_81_90integerНеобязательныйnumber of organic SERPs where the domain ranks #81-90
pos_91_100integerНеобязательныйnumber of organic SERPs where the domain ranks #91-100
etvnumberНеобязательныйestimated traffic volume estimated organic monthly traffic to the domain calculated as the product of CTR (click-through-rate) and search volume values of all keywords the domain ranks for learn more about how the metric is calculated in this help center article
countintegerНеобязательныйtotal count of organic SERPs that contain the domain
estimated_paid_traffic_costnumberНеобязательныйestimated cost of converting organic search traffic into paid represents the estimated monthly cost of running ads (USD) for all keywords a domain ranks for the metric is calculated as the product of organic etv and paid cpc values and indicates the cost of driving the estimated volume of monthly organic traffic through PPC advertising in Google Search learn more about how the metric is calculated in this help center article
paidobjectНеобязательныйranking and traffic data from paid search
pos_1integerНеобязательныйnumber of paid SERPs where the domain ranks #1
pos_2_3integerНеобязательныйnumber of paid SERPs where the domain ranks #2-3
pos_4_10integerНеобязательныйnumber of paid SERPs where the domain ranks #4-10
pos_11_20integerНеобязательныйnumber of paid SERPs where the domain ranks #11-20
pos_21_30integerНеобязательныйnumber of paid SERPs where the domain ranks #21-30
pos_31_40integerНеобязательныйnumber of paid SERPs where the domain ranks #31-40
pos_41_50integerНеобязательныйnumber of paid SERPs where the domain ranks #41-50
pos_51_60integerНеобязательныйnumber of paid SERPs where the domain ranks #51-60
pos_61_70integerНеобязательныйnumber of paid SERPs where the domain ranks #61-70
pos_71_80integerНеобязательныйnumber of paid SERPs where the domain ranks #71-80
pos_81_90integerНеобязательныйnumber of paid SERPs where the domain ranks #81-90
pos_91_100integerНеобязательныйnumber of paid SERPs where the domain ranks #91-100
etvnumberНеобязательныйestimated traffic volume estimated paid monthly traffic to the domain calculated as the product of CTR (click-through-rate) and search volume values of all keywords the domain ranks for learn more about how the metric is calculated in this help center article
countintegerНеобязательныйtotal count of paid SERPs that contain the domain
estimated_paid_traffic_costnumberНеобязательныйestimated cost of monthly search traffic represents the estimated cost of paid monthly traffic (USD) based on etv and cpc values learn more about how the metric is calculated in this help center article
backlinks_infoobjectНеобязательныйbacklink data for the returned domain
referring_domainsintegerНеобязательныйnumber of referring domains
referring_main_domainsintegerНеобязательныйnumber of referring main domains
referring_pagesintegerНеобязательныйnumber of referring pages
dofollowintegerНеобязательныйnumber of dofollow links
backlinksintegerНеобязательныйtotal number of backlinks the total number of backlinks, including dofollow and nofollow links
time_updatestringНеобязательныйdate and time when backlink data was updated in the UTC format: "yyyy-mm-dd hh-mm-ss +00:00" example: 2019-11-15 12:57:46 +00:00