{"id":15560,"date":"2022-10-19T13:26:19","date_gmt":"2022-10-19T13:26:19","guid":{"rendered":"https:\/\/docs_v3.dataforseo.com\/v3\/?page_id=15560"},"modified":"2026-08-07T14:56:15","modified_gmt":"2026-08-07T14:56:15","slug":"domain_analytics-whois-filters","status":"publish","type":"page","link":"https:\/\/docs.dataforseo.com\/v3\/domain_analytics-whois-filters\/","title":{"rendered":"domain_analytics\/whois\/filters\/"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><p>[vc_row][vc_column][vc_column_text]<\/p>\n<h2 id=\"live-serp\">Filters for Domain Analytics Whois API<\/h2>\n<p>\u200c\u200c<br \/>\nHere you will find all the necessary information about filters that can be used with Domain Analytics Whois API.<\/p>\n<p>Note that filters are associated with a certain object in the <code>result<\/code> array, and should be specified accordingly.<br \/>\n[\/vc_column_text]\t<article class=\"info-card info-card--yellow\">\n\t\t<header class=\"info-card__header\">\n\t\t\t<div class=\"info-card__icon\">\n\t\t\t\t<svg width=\"16\" height=\"16\" viewBox=\"0 0 16 16\">\n\t\t\t\t\t<use href=\"https:\/\/docs.dataforseo.com\/v3\/wp-content\/themes\/dataforseo\/assets\/img\/icons\/sprite.svg#label\"><\/use>\n\t\t\t\t<\/svg>\n\t\t\t<\/div>\n\t\t\t<div class=\"info-card__title\">Pricing<\/div>\n\t\t<\/header>\n\t\t<div class=\"info-card__content\">\n\t\t\t<p>Your account will not be charged for using this API<\/p>\n\t\t<\/div>\n\t<\/article>\n\t    <div class=\"endpoint\">\n        <img decoding=\"async\" class=\"endpoint__icon\" src=\"https:\/\/docs.dataforseo.com\/v3\/wp-content\/themes\/dataforseo\/assets\/img\/icons\/checked-circle.svg\" alt=\"checked\">\n\n                    GET            <button class=\"btn-reset button-link copy-button\" data-href=\"https:\/\/api.dataforseo.com\/v3\/domain_analytics\/whois\/available_filters\">\n                https:\/\/api.dataforseo.com\/v3\/domain_analytics\/whois\/available_filters                <svg width=\"16\" height=\"16\" viewBox=\"0 0 16 16\">\n                    <use href=\"https:\/\/docs.dataforseo.com\/v3\/wp-content\/themes\/dataforseo\/assets\/img\/icons\/sprite.svg#layers\"><\/use>\n                <\/svg>\n            <\/button>\n            <\/div>\n    [vc_column_text] You will receive the full list of filters by calling this API. You can also download the full list of possible filters <a href=\"https:\/\/cdn.dataforseo.com\/v3\/available_filters.php?api=domain_analytics\/whois\">by this link.<\/a><\/p>\n<p>\u200c\u200cAs a response of the API server, you will receive <a href=\"https:\/\/en.wikipedia.org\/wiki\/JSON\">JSON<\/a>-encoded data containing a <code>tasks<\/code> array with the information specific to the set tasks.<br \/>\n<div class=\"dfs-doc-container dfs-doc-request\"><table><thead><tr><th>Field name<\/th><th>Type<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr data-doc-id=\"version\"><td><code>version<\/code><\/td><td>string<\/td><td><p><em>the current version of the API<\/em><\/p><\/td><\/tr><tr data-doc-id=\"status_code\"><td><code>status_code<\/code><\/td><td>integer<\/td><td><p><i>general status code<\/i><br>you can find the full list of the response codes <a href=\"\/v3\/appendix\/errors\">here<\/a><\/p><\/td><\/tr><tr data-doc-id=\"status_message\"><td><code>status_message<\/code><\/td><td>string<\/td><td><p><em>general informational message<\/em><br>you can find the full list of general informational messages <a href=\"\/v3\/appendix\/errors\">here<\/a><\/p><\/td><\/tr><tr data-doc-id=\"time\"><td><code>time<\/code><\/td><td>string<\/td><td><p><em>execution time, seconds<\/em><\/p><\/td><\/tr><tr data-doc-id=\"cost\"><td><code>cost<\/code><\/td><td>float<\/td><td><p><em>total tasks cost, USD<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks_count\"><td><code>tasks_count<\/code><\/td><td>integer<\/td><td><p><em>the number of tasks in the <strong><code>tasks<\/code><\/strong> array<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks_error\"><td><code>tasks_error<\/code><\/td><td>integer<\/td><td><p><em>the number of tasks in the <strong><code>tasks<\/code><\/strong> array returned with an error<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks\"><td><strong><code>tasks<\/code><\/strong><\/td><td>array<\/td><td><p><em>array of tasks<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-id\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>id<\/code><\/td><td>string<\/td><td><p><em>task identifier<\/em><br><strong>unique task identifier in our system in the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Universally_unique_identifier\">UUID<\/a> format<\/strong><\/p><\/td><\/tr><tr data-doc-id=\"tasks-status_code\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>status_code<\/code><\/td><td>integer<\/td><td><p><em>status code of the task<\/em><br>generated by DataForSEO; can be within the following range: 10000-60000<br>you can find the full list of the response codes <a href=\"\/v3\/appendix\/errors\">here<\/a><\/p><\/td><\/tr><tr data-doc-id=\"tasks-status_message\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>status_message<\/code><\/td><td>string<\/td><td><p><em>informational message of the task<\/em><br>you can find the full list of general informational messages <a href=\"\/v3\/appendix\/errors\">here<\/a><\/p><\/td><\/tr><tr data-doc-id=\"tasks-time\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>time<\/code><\/td><td>string<\/td><td><p><em>execution time, seconds<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-cost\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>cost<\/code><\/td><td>float<\/td><td><p><em>cost of the task, USD<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-result_count\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>result_count<\/code><\/td><td>integer<\/td><td><p><em>number of elements in the <code>result<\/code> array<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-path\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>path<\/code><\/td><td>array<\/td><td><p><em>URL path<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-data\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>data<\/code><\/td><td>object<\/td><td><p><em>contains the parameters passed in the URL of the GET request<\/em><\/p><\/td><\/tr><tr data-doc-id=\"tasks-result\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>result<\/code><\/td><td>array<\/td><td><p><em>array of results<\/em><br>contains the full list of available parameters that can be used for data filtration<br>the parameters are grouped by the endpoint they can be used with<\/p><\/td><\/tr><\/tbody><\/table><\/div><br \/>\n&thinsp;<br \/>\nBelow you will find a detailed description of the structure that should be used to specify filters for Domain Analytics Whois API. You will also find the types of parameters that can be used with each endpoint, and examples of pre-made filters. <\/p>\n<p><strong>Description of the fields:<\/strong><br \/>\n<div class=\"dfs-doc-container dfs-doc-response\"><div class=\"api-block-main\"><div class=\"api-section\"><table><thead><tr><th>Field name<\/th><th>Type<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr data-doc-id=\"filters\"><td><strong><code>filters<\/code><\/strong><\/td><td>array<\/td><td><p><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>filters have the following structure:<br><code>[<\/code><code>$item_array<\/code><code>.<\/code><code>$results_array<\/code><code>.<\/code><code>$parameter_field<\/code><code>,<\/code> <code>$filter_operator<\/code><code>,<\/code> <code>$filter_value<\/code><code>]<\/code><br>you should use the <code>.<\/code> and <code>,<\/code> characters as separators<br>example:<br><code>[\"metrics.organic.pos_1\", \">=\", 50]<\/code><\/p><\/td><\/tr><tr data-doc-id=\"filters-$item_array\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>$item_array<\/code><\/td><td>str<\/td><td><p><em>item name in the filter<\/em><br>optional field<br>possible values:<br><code>keyword_data<\/code>, <code>ranked_serp_element<\/code><\/p><\/td><\/tr><tr data-doc-id=\"filters-$results_array\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>$results_array<\/code><\/td><td>str<\/td><td><p><em>results array in the filter<\/em><br>optional field<br>possible values:<br><code>keyword<\/code>, <code>keyword_info<\/code>, <code>check_url<\/code>, <code>se_results_count<\/code>, <code>serp_item<\/code>, <code>metrics<\/code><\/p><\/td><\/tr><tr data-doc-id=\"filters-$parameter_field\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>$parameter_field<\/code><\/td><td>str<\/td><td><p><em>parameter field in the filter<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong><br>the parameter in the superordinate <code>$results_array<\/code> or <code>item_array<\/code><br>represents the field you want to filter the results by<\/p><\/td><\/tr><tr data-doc-id=\"filters-$filter_operator\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>$filter_operator<\/code><\/td><td>str<\/td><td><p><em>operator in the filter<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong><br>available filter operators:<br>\u2022 if <strong><code>bool<\/code><\/strong>: <code>=<\/code>, <code><><\/code><br>\u2022 if <strong><code>num<\/code><\/strong>: <code><<\/code>, <code><=<\/code>, <code>><\/code>, <code>>=<\/code>, <code>=<\/code>, <code><><\/code>, <code>in<\/code>, <code>not_in<\/code><br>\u2022 if <strong><code>str<\/code><\/strong>: <code>like<\/code>, <code>not_like<\/code>, <code>in<\/code>, <code>not_in<\/code>, <code>=<\/code>, <code><><\/code>, <code>regex<\/code>, <code>not_regex<\/code><br>\u2022 if <strong><code>array.str<\/code><\/strong>: <code>has<\/code>, <code>has_not<\/code><br>\u2022 if <strong><code>array.num<\/code><\/strong>: <code>has<\/code>, <code>has_not<\/code><br>\u2022 if <strong><code>time<\/code><\/strong>: <code><<\/code>, <code>><\/code><code>time<\/code> should be specified in the format: \u201cyyyy-mm-dd hh-mm-ss +00:00\u201d<br>example:<br><code>2021-01-29 15:02:37 +00:00<\/code><p>if you specify <code>in<\/code> or <code>not_in<\/code> operator, the <code>$filter_value<\/code> should be specified as an array;<br>example:<br><code>[\"metrics.organic.etv\",\"in\",[10,100]]<\/code><p><code>regex<\/code> and <code>not_regex<\/code> operator can be specified with <code>string<\/code> values using the <a href=\"https:\/\/github.com\/google\/re2\/wiki\/Syntax\" rel=\"noopener noreferrer\" target=\"_blank\">RE2 regex<\/a> syntax;<br><strong>Note:<\/strong> the maximum limit for the number of characters you can specify in <code>regex<\/code> and <code>not_regex<\/code> is <strong>1000<\/strong>;<br> <br><code>like<\/code> and <code>not_like<\/code> operators require adding <code>%<\/code> character to get accurate results;<br>example:<br><code>[\"domain\", \"like\", \"%seo%\"]<\/code> return <code>keyword_data<\/code> items that contain \u201cseo\u201d in the <code>domain<\/code> field<br><code>[\"domain\", \"not_like\", \"%seo%\"]<\/code> do not return domains that contain \u201cseo\u201d<\/p><\/td><\/tr><tr data-doc-id=\"filters-$filter_value\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>$filter_value<\/code><\/td><td>num str bool array.str<\/td><td><p><em>filtering value<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong><\/p><\/td><\/tr><tr data-doc-id=\"filters-available_filters\"><td>&nbsp;&nbsp;&nbsp;&nbsp;<code>available_filters<\/code><\/td><td>num str bool<\/td><td><p><em>the list of available filters for the <a href=\"\/v3\/domain_analytics\/whois\/overview\/live\/\">Domain Analytics Whois Overview<\/a> endpoint:<\/em><br><code>[\"domain\", \"like\", \"%seo%\"]<br>[\"expiration_datetime\",\">\",\"2021-02-15 01:00:00 +00:00\"]<br>[\"created_datetime\",\"<\",\"2019-03-15 01:00:00 +00:00\"]<br>[\"registered\",\"=\",true]<br>[\"tld\",\"=\",\"com\"]<br>[\"metrics.organic.etv\",\">\",100]<br>[\"metrics.paid.etv\",\">\",0]<\/code><br>You can get the full list of possible filters <a href=\"https:\/\/cdn.dataforseo.com\/v3\/available_filters.php?api=dataforseo_labs\" target=\"_blank\" rel=\"noopener noreferrer\">by this link<\/a><\/p><\/td><\/tr><\/tbody><\/table><\/div><\/div><\/div><br \/>\n\u200c\u200c[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<blockquote><p>Instead of \u2018login\u2019 and \u2018password\u2019 use your credentials from https:\/\/app.dataforseo.com\/api-access<\/p><\/blockquote><blockquote><p>The list of available filtration parameters:<\/p><\/blockquote><div class=\"example example--json\"><div class=\"example__content\"><div class=\"example__code example__code-json\"><pre><code class=\"language-json hljs\">{\r\n    &quot;version&quot;: &quot;0.1.20220819&quot;,\r\n    &quot;status_code&quot;: 20000,\r\n    &quot;status_message&quot;: &quot;Ok.&quot;,\r\n    &quot;time&quot;: &quot;0.0594 sec.&quot;,\r\n    &quot;cost&quot;: 0,\r\n    &quot;tasks_count&quot;: 1,\r\n    &quot;tasks_error&quot;: 0,\r\n    &quot;tasks&quot;: [\r\n        {\r\n            &quot;id&quot;: &quot;10191600-1535-0493-0000-443468ba069f&quot;,\r\n            &quot;status_code&quot;: 20000,\r\n            &quot;status_message&quot;: &quot;Ok.&quot;,\r\n            &quot;time&quot;: &quot;0 sec.&quot;,\r\n            &quot;cost&quot;: 0,\r\n            &quot;result_count&quot;: 1,\r\n            &quot;path&quot;: [\r\n                &quot;v3&quot;,\r\n                &quot;domain_analytics&quot;,\r\n                &quot;whois&quot;,\r\n                &quot;available_filters&quot;\r\n            ],\r\n            &quot;data&quot;: {\r\n                &quot;api&quot;: &quot;domain_analytics&quot;,\r\n                &quot;function&quot;: &quot;available_filters&quot;,\r\n                &quot;se&quot;: &quot;whois&quot;\r\n            },\r\n            &quot;result&quot;: [\r\n                {\r\n                    &quot;overview&quot;: {\r\n                        &quot;domain&quot;: &quot;str&quot;,\r\n                        &quot;created_datetime&quot;: &quot;time&quot;,\r\n                        &quot;changed_datetime&quot;: &quot;time&quot;,\r\n                        &quot;expiration_datetime&quot;: &quot;time&quot;,\r\n                        &quot;updated_datetime&quot;: &quot;time&quot;,\r\n                        &quot;epp_status_codes&quot;: &quot;array.str&quot;,\r\n                        &quot;tld&quot;: &quot;str&quot;,\r\n                        &quot;registered&quot;: &quot;bool&quot;,\r\n                        &quot;registrar&quot;: &quot;str&quot;,\r\n                        &quot;metrics.paid.pos_1&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_2_3&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_4_10&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_11_20&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_21_30&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_31_40&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_41_50&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_51_60&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_61_70&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_71_80&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_81_90&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.pos_91_100&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.etv&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.count&quot;: &quot;num&quot;,\r\n                        &quot;metrics.paid.estimated_paid_traffic_cost&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_1&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_2_3&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_4_10&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_11_20&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_21_30&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_31_40&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_41_50&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_51_60&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_61_70&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_71_80&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_81_90&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.pos_91_100&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.etv&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.count&quot;: &quot;num&quot;,\r\n                        &quot;metrics.organic.estimated_paid_traffic_cost&quot;: &quot;num&quot;\r\n                    }\r\n                }\r\n            ]\r\n        }\r\n    ]\r\n}<\/code><\/pre><\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>[vc_row][vc_column][vc_column_text] Filters for Domain Analytics Whois API \u200c\u200c Here you will find all the necessary information about filters that can be used with Domain Analytics Whois API. Note that filters are associated with a certain object in the result array, and should be specified accordingly. [\/vc_column_text] Pricing Your account will not be charged for using [&hellip;]<\/p>\n","protected":false},"author":17,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template.php","meta":{"apibase_doc_request_yaml":"parameters:\n  - name: version\n    type: string\n    description: |\n      <em>the current version of the API<\/em>\n  - name: status_code\n    type: integer\n    description: |\n      <i>general status code<\/i><br>you can find the full list of the response codes <a href=\"\/v3\/appendix\/errors\">here<\/a>\n  - name: status_message\n    type: string\n    description: |\n      <em>general informational message<\/em><br>you can find the full list of general informational messages <a href=\"\/v3\/appendix\/errors\">here<\/a>\n  - name: time\n    type: string\n    description: |\n      <em>execution time, seconds<\/em>\n  - name: cost\n    type: float\n    description: |\n      <em>total tasks cost, USD<\/em>\n  - name: tasks_count\n    type: integer\n    description: |\n      <em>the number of tasks in the <strong><code>tasks<\/code><\/strong> array<\/em>\n  - name: tasks_error\n    type: integer\n    description: |\n      <em>the number of tasks in the <strong><code>tasks<\/code><\/strong> array returned with an error<\/em>\n  - name: tasks\n    type: array\n    description: |\n      <em>array of tasks<\/em>\n    items:\n      children:\n        - name: id\n          type: string\n          description: |\n            <em>task identifier<\/em><br><strong>unique task identifier in our system in the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Universally_unique_identifier\">UUID<\/a> format<\/strong>\n        - name: status_code\n          type: integer\n          description: |\n            <em>status code of the task<\/em><br>generated by DataForSEO; can be within the following range: 10000-60000<br>you can find the full list of the response codes <a href=\"\/v3\/appendix\/errors\">here<\/a>\n        - name: status_message\n          type: string\n          description: |\n            <em>informational message of the task<\/em><br>you can find the full list of general informational messages <a href=\"\/v3\/appendix\/errors\">here<\/a>\n        - name: time\n          type: string\n          description: |\n            <em>execution time, seconds<\/em>\n        - name: cost\n          type: float\n          description: |\n            <em>cost of the task, USD<\/em>\n        - name: result_count\n          type: integer\n          description: |\n            <em>number of elements in the <code>result<\/code> array<\/em>\n        - name: path\n          type: array\n          description: |\n            <em>URL path<\/em>\n        - name: data\n          type: object\n          description: |\n            <em>contains the parameters passed in the URL of the GET request<\/em>\n        - name: result\n          type: array\n          description: |\n            <em>array of results<\/em><br>contains the full list of available parameters that can be used for data filtration<br>the parameters are grouped by the endpoint they can be used with","apibase_doc_request_additional_yaml":"","apibase_doc_response_yaml":"parameters:\n  - name: filters\n    type: array\n    description: |\n      <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>filters have the following structure:<br><code>[<\/code><code>$item_array<\/code><code>.<\/code><code>$results_array<\/code><code>.<\/code><code>$parameter_field<\/code><code>,<\/code> <code>$filter_operator<\/code><code>,<\/code> <code>$filter_value<\/code><code>]<\/code><br>you should use the <code>.<\/code> and <code>,<\/code> characters as separators<br>example:<br><code>[\"metrics.organic.pos_1\", \"&gt;=\", 50]<\/code>\n    items:\n      children:\n        - name: $item_array\n          type: str\n          description: |\n            <em>item name in the filter<\/em><br>optional field<br>possible values:<br><code>keyword_data<\/code>, <code>ranked_serp_element<\/code>\n        - name: $results_array\n          type: str\n          description: |\n            <em>results array in the filter<\/em><br>optional field<br>possible values:<br><code>keyword<\/code>, <code>keyword_info<\/code>, <code>check_url<\/code>, <code>se_results_count<\/code>, <code>serp_item<\/code>, <code>metrics<\/code>\n        - name: $parameter_field\n          type: str\n          description: |\n            <em>parameter field in the filter<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong><br>the parameter in the superordinate <code>$results_array<\/code> or <code>item_array<\/code><br>represents the field you want to filter the results by\n        - name: $filter_operator\n          type: str\n          description: |\n            <em>operator in the filter<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong><br>available filter operators:<br>\u2022 if <strong><code>bool<\/code><\/strong>: <code>=<\/code>, <code>&lt;&gt;<\/code><br>\u2022 if <strong><code>num<\/code><\/strong>: <code>&lt;<\/code>, <code>&lt;=<\/code>, <code>&gt;<\/code>, <code>&gt;=<\/code>, <code>=<\/code>, <code>&lt;&gt;<\/code>, <code>in<\/code>, <code>not_in<\/code><br>\u2022 if <strong><code>str<\/code><\/strong>: <code>like<\/code>, <code>not_like<\/code>, <code>in<\/code>, <code>not_in<\/code>, <code>=<\/code>, <code>&lt;&gt;<\/code>, <code>regex<\/code>, <code>not_regex<\/code><br>\u2022 if <strong><code>array.str<\/code><\/strong>: <code>has<\/code>, <code>has_not<\/code><br>\u2022 if <strong><code>array.num<\/code><\/strong>: <code>has<\/code>, <code>has_not<\/code><br>\u2022 if <strong><code>time<\/code><\/strong>: <code>&lt;<\/code>, <code>&gt;<\/code><code>time<\/code> should be specified in the format: \u201cyyyy-mm-dd hh-mm-ss +00:00\u201d<br>example:<br><code>2021-01-29 15:02:37 +00:00<\/code><p>if you specify <code>in<\/code> or <code>not_in<\/code> operator, the <code>$filter_value<\/code> should be specified as an array;<br>example:<br><code>[\"metrics.organic.etv\",\"in\",[10,100]]<\/code><p><code>regex<\/code> and <code>not_regex<\/code> operator can be specified with <code>string<\/code> values using the <a href=\"https:\/\/github.com\/google\/re2\/wiki\/Syntax\" rel=\"noopener noreferrer\" target=\"_blank\">RE2 regex<\/a> syntax;<br><strong>Note:<\/strong> the maximum limit for the number of characters you can specify in <code>regex<\/code> and <code>not_regex<\/code> is <strong>1000<\/strong>;<br> <br><code>like<\/code> and <code>not_like<\/code> operators require adding <code>%<\/code> character to get accurate results;<br>example:<br><code>[\"domain\", \"like\", \"%seo%\"]<\/code> return <code>keyword_data<\/code> items that contain \u201cseo\u201d in the <code>domain<\/code> field<br><code>[\"domain\", \"not_like\", \"%seo%\"]<\/code> do not return domains that contain \u201cseo\u201d\n        - name: $filter_value\n          type: num str bool array.str\n          description: |\n            <em>filtering value<\/em><br>optional field<br><strong>required field if the filter is applied<\/strong>\n        - name: available_filters\n          type: num str bool\n          description: |\n            <em>the list of available filters for the <a href=\"\/v3\/domain_analytics\/whois\/overview\/live\/\">Domain Analytics Whois Overview<\/a> endpoint:<\/em><br><code>[\"domain\", \"like\", \"%seo%\"]<br>[\"expiration_datetime\",\"&gt;\",\"2021-02-15 01:00:00 +00:00\"]<br>[\"created_datetime\",\"&lt;\",\"2019-03-15 01:00:00 +00:00\"]<br>[\"registered\",\"=\",true]<br>[\"tld\",\"=\",\"com\"]<br>[\"metrics.organic.etv\",\"&gt;\",100]<br>[\"metrics.paid.etv\",\"&gt;\",0]<\/code><br>You can get the full list of possible filters <a href=\"https:\/\/cdn.dataforseo.com\/v3\/available_filters.php?api=dataforseo_labs\" target=\"_blank\" rel=\"noopener noreferrer\">by this link<\/a>","footnotes":""},"class_list":["post-15560","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/pages\/15560","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/comments?post=15560"}],"version-history":[{"count":16,"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/pages\/15560\/revisions"}],"predecessor-version":[{"id":26229,"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/pages\/15560\/revisions\/26229"}],"wp:attachment":[{"href":"https:\/\/docs.dataforseo.com\/v3\/wp-json\/wp\/v2\/media?parent=15560"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}