{ "consumes": [ "application/json" ], "produces": [ "application/json" ], "schemes": [ "https" ], "swagger": "2.0", "info": { "description": "An extension of the Infoblox Threat Defense Suite, Infoblox LAD is used to detect lookalike domains. You can subscribe to Infoblox LAD and use its functionality to protect domains from spoofing threats.\n\n", "title": "Infoblox LAD API", "version": "v1" }, "basePath": "/api/tdlad/v1/", "paths": { "/lookalike_domains": { "get": { "description": "Use this method to retrieve information about all detected Lookalike Domain objects with target domains specified by the account.\n", "tags": [ "lookalike_domains" ], "summary": "Lookalike Domain Lists.", "operationId": "lookalike_domainsListLookalikeDomain", "parameters": [ { "type": "string", "description": "A collection of response resources can be filtered by a logical expression string that includes JSON tag references to values in each resource, literal values, and logical operators. If a resource does not have the specified tag, its value is assumed to be null.\n\nLiteral values include numbers (integer and floating-point), and quoted (both single- or double-quoted) literal strings, and 'null'.\n\nYou can filter by following fields:\n\n| Name | type | Supported Ops |\n| -------------- | ------------------------------ | --------------------------- |\n| reason | string | ==, !=, ~, !~ |\n| target_domain | string | ==, !=, ~, !~, \u003e, \u003c, \u003c=, \u003e= |\n| lookalike_host | string | ==, !=, ~, !~, \u003e, \u003c, \u003c=, \u003e= |\n| detected_at | string (iso/rfc3339 timestamp) | ==, \u003c, \u003e, \u003c=, \u003e= |\n", "name": "_filter", "in": "query" }, { "type": "string", "description": "\n\nA collection of response resources can be transformed by specifying a set of JSON tags to be returned. For a “flat” resource, the tag name is straightforward. If field selection is allowed on non-flat hierarchical resources, the service should implement a qualified naming scheme such as dot-qualification to reference data down the hierarchy. If a resource does not have the specified tag, the tag does not appear in the output resource.\n\nSpecify this parameter as a comma-separated list of JSON tag names.\n\n\t\t\t\t\t\t", "name": "_fields", "in": "query" }, { "type": "integer", "description": "\n\nThe integer index (zero-origin) of the offset into a collection of resources. If omitted or null the value is assumed to be '0'.\n\n\t\t\t\t\t\t\t", "name": "_offset", "in": "query" }, { "type": "integer", "description": "\n\nThe integer number of resources to be returned in the response. The service may impose maximum value. If omitted the service may impose a default value.\n\n\t\t\t\t\t\t\t", "name": "_limit", "in": "query" }, { "type": "string", "description": "\n\nThe service-defined string used to identify a page of resources. A null value indicates the first page.\n\n\t\t\t\t\t\t\t", "name": "_page_token", "in": "query" }, { "type": "string", "description": "\n\nA collection of response resources can be sorted by their JSON tags. For a 'flat' resource, the tag name is straightforward. If sorting is allowed on non-flat hierarchical resources, the service should implement a qualified naming scheme such as dot-qualification to reference data down the hierarchy. If a resource does not have the specified tag, its value is assumed to be null.)\n\nSpecify this parameter as a comma-separated list of JSON tag names. The sort direction can be specified by a suffix separated by whitespace before the tag name. The suffix 'asc' sorts the data in ascending order. The suffix 'desc' sorts the data in descending order. If no suffix is specified the data is sorted in ascending order.\n\n\t\t\t\t\t\t", "name": "_order_by", "in": "query" } ], "responses": { "200": { "description": "GET operation response", "schema": { "$ref": "#/definitions/serviceLookalikeDomainReadMultiResponse" } } } } }, "/lookalike_target_candidates": { "get": { "description": "Use this method to retrieve information on all Lookalike Target Candidates.\n\nThe Lookalike Target Candidates are second-level domains against which Infoblox detects lookalike FQDNs.\n", "tags": [ "lookalike_target_candidates" ], "summary": "List Lookalike Target Candidates.", "operationId": "lookalike_target_candidatesListLookalikeCandidates", "parameters": [ { "type": "string", "description": "A collection of response resources can be sorted by a space separated field-ordering pair.\n\nOrdering can be either 'asc' (for ascended order: 'A' to 'Z' for strings, and 0 to 9 for numbers) or 'desc' (for descended order).\n\nYou can sort by following fields:\n\n| Name | description |\n| ---------------- | ----------------------------- |\n| domain | Sort by domain |\n\nExample:\n```\n?_order_by=domain asc\n```\n", "name": "_order_by", "in": "query" }, { "type": "string", "description": "\n\nA collection of response resources can be filtered by a logical expression string that includes JSON tag references to values in each resource, literal values, and logical operators. If a resource does not have the specified tag, its value is assumed to be null.\n\nLiteral values include numbers (integer and floating-point), and quoted (both single- or double-quoted) literal strings, and 'null'. The following operators are commonly used in filter expressions:\n\n| Op | Description | \n| -- | ----------- | \n| == | Equal | \n| != | Not Equal | \n| \u003e | Greater Than | \n| \u003e= | Greater Than or Equal To | \n| \u003c | Less Than | \n| \u003c= | Less Than or Equal To | \n| and | Logical AND | \n| ~ | Matches Regex | \n| !~ | Does Not Match Regex | \n| or | Logical OR | \n| not | Logical NOT | \n| () | Groupping Operators |\n\n\t\t\t\t\t\t", "name": "_filter", "in": "query" }, { "type": "boolean", "format": "boolean", "description": "Determines whether account-specific or common candidates are to be returned. The default value is \\\"false\\\": common candidates are to be returned.", "name": "account_specific", "in": "query" } ], "responses": { "200": { "description": "GET operation response", "schema": { "$ref": "#/definitions/serviceLookalikeCandidatesReadResponse" } } } }, "patch": { "description": "Use this method to update an existing list of Lookalike Target Candidates.\n\nThe Lookalike Target Candidates are second-level domains against which Infoblox detects lookalike FQDNs.", "tags": [ "lookalike_target_candidates" ], "summary": "Update Lookalike Target Candidates.", "operationId": "lookalike_target_candidatesUpdateLookalikeCandidates", "parameters": [ { "name": "body", "in": "body", "required": true, "schema": { "$ref": "#/definitions/serviceLookalikeCandidatesUpdateRequest" } } ], "responses": { "201": { "description": "PATCH operation response", "schema": { "$ref": "#/definitions/serviceLookalikeCandidatesUpdateResponse" } } } } }, "/lookalike_targets": { "get": { "description": "Use this method to retrieve information about all Lookalike Target Domains for the account.\n\nThe lookalike target domains are second-level domains against which Infoblox detects lookalike FQDNs.\n", "tags": [ "lookalike_targets" ], "summary": "List Lookalike Target Domains.", "operationId": "lookalike_targetsListLookalikeTargets", "parameters": [ { "type": "string", "description": "\n\nA collection of response resources can be transformed by specifying a set of JSON tags to be returned. For a “flat” resource, the tag name is straightforward. If field selection is allowed on non-flat hierarchical resources, the service should implement a qualified naming scheme such as dot-qualification to reference data down the hierarchy. If a resource does not have the specified tag, the tag does not appear in the output resource.\n\nSpecify this parameter as a comma-separated list of JSON tag names.\n\n\t\t\t\t\t\t", "name": "_fields", "in": "query" }, { "type": "string", "description": "A collection of response resources can be sorted by a space separated field-ordering pair.\n\nOrdering can be either 'asc' (for ascended order: 'A' to 'Z' for strings, and 0 to 9 for numbers) or 'desc' (for descended order).\n\nYou can sort by following fields:\n\n| Name | description |\n| ---------------- | ----------------------------- |\n| domain | Sort by domain |\n| description | Sort by description |\n\nExample:\n```\n?_order_by=data asc\n```\n", "name": "_order_by", "in": "query" } ], "responses": { "200": { "description": "GET operation response", "schema": { "$ref": "#/definitions/serviceLookalikeTargetsReadResponse" } } } }, "put": { "description": "Use this method to update the existing list Lookalike Target Domains. Duplicated items are skipped silently, and only new items are appended to the list.\n\nThe lookalike target domains are second-level domains against which Infoblox detects lookalike FQDNs.\n", "tags": [ "lookalike_targets" ], "summary": "Update Lookalike Target Domains.", "operationId": "lookalike_targetsUpdateLookalikeTargets", "parameters": [ { "name": "body", "in": "body", "required": true, "schema": { "$ref": "#/definitions/serviceLookalikeTargetsUpdateRequest" } } ], "responses": { "201": { "description": "PUT operation response", "schema": { "$ref": "#/definitions/serviceLookalikeTargetsUpdateResponse" } }, "400": { "description": "\n- 'items' value must contain only second level domain names where the second-level has length equal or greater than 5.", "schema": { "properties": { "error": { "type": "object", "properties": { "code": { "type": "string", "example": "INVALID_ARGUMENT" }, "message": { "type": "string", "example": "Lookalike watch domain must be a second-level domain longer than 4 characters" }, "status": { "type": "string", "example": 400 } } } } } }, "500": { "description": "\n- Internal server error occurred", "schema": { "properties": { "error": { "type": "object", "properties": { "code": { "type": "string", "example": "INTERNAL" }, "message": { "type": "string", "example": "Internal Server Error" }, "status": { "type": "string", "example": 500 } } } } } } } } }, "/lookalikes": { "get": { "tags": [ "lookalike_domains" ], "operationId": "lookalike_domainsGetLookalikeDomains", "parameters": [ { "type": "string", "description": "\n\nA collection of response resources can be filtered by a logical expression string that includes JSON tag references to values in each resource, literal values, and logical operators. If a resource does not have the specified tag, its value is assumed to be null.\n\nLiteral values include numbers (integer and floating-point), and quoted (both single- or double-quoted) literal strings, and 'null'. The following operators are commonly used in filter expressions:\n\n| Op | Description | \n| -- | ----------- | \n| == | Equal | \n| != | Not Equal | \n| \u003e | Greater Than | \n| \u003e= | Greater Than or Equal To | \n| \u003c | Less Than | \n| \u003c= | Less Than or Equal To | \n| and | Logical AND | \n| ~ | Matches Regex | \n| !~ | Does Not Match Regex | \n| or | Logical OR | \n| not | Logical NOT | \n| () | Groupping Operators |\n\n\t\t\t\t\t\t", "name": "_filter", "in": "query" }, { "type": "string", "description": "\n\nA collection of response resources can be transformed by specifying a set of JSON tags to be returned. For a “flat” resource, the tag name is straightforward. If field selection is allowed on non-flat hierarchical resources, the service should implement a qualified naming scheme such as dot-qualification to reference data down the hierarchy. If a resource does not have the specified tag, the tag does not appear in the output resource.\n\nSpecify this parameter as a comma-separated list of JSON tag names.\n\n\t\t\t\t\t\t", "name": "_fields", "in": "query" }, { "type": "integer", "description": "\n\nThe integer index (zero-origin) of the offset into a collection of resources. If omitted or null the value is assumed to be '0'.\n\n\t\t\t\t\t\t\t", "name": "_offset", "in": "query" }, { "type": "integer", "description": "\n\nThe integer number of resources to be returned in the response. The service may impose maximum value. If omitted the service may impose a default value.\n\n\t\t\t\t\t\t\t", "name": "_limit", "in": "query" }, { "type": "string", "description": "\n\nThe service-defined string used to identify a page of resources. A null value indicates the first page.\n\n\t\t\t\t\t\t\t", "name": "_page_token", "in": "query" }, { "type": "string", "description": "\n\nA collection of response resources can be sorted by their JSON tags. For a 'flat' resource, the tag name is straightforward. If sorting is allowed on non-flat hierarchical resources, the service should implement a qualified naming scheme such as dot-qualification to reference data down the hierarchy. If a resource does not have the specified tag, its value is assumed to be null.)\n\nSpecify this parameter as a comma-separated list of JSON tag names. The sort direction can be specified by a suffix separated by whitespace before the tag name. The suffix 'asc' sorts the data in ascending order. The suffix 'desc' sorts the data in descending order. If no suffix is specified the data is sorted in ascending order.\n\n\t\t\t\t\t\t", "name": "_order_by", "in": "query" } ], "responses": { "200": { "description": "GET operation response", "schema": { "$ref": "#/definitions/serviceGetLookalikeDomainsResponse" } } } }, "patch": { "description": "Use this method to hide or expose lookalikes.", "tags": [ "lookalike_domains" ], "summary": "Update Lookalike Domain.", "operationId": "lookalike_domainsUpdateLookalikeDomains", "parameters": [ { "name": "body", "in": "body", "required": true, "schema": { "$ref": "#/definitions/serviceLookalikeDomainUpdateRequest" } } ], "responses": { "201": { "description": "PATCH operation response", "schema": { "$ref": "#/definitions/serviceLookalikeDomainUpdateResponse" } } } } } }, "definitions": { "protobufFieldMask": { "description": "paths: \"f.a\"\n paths: \"f.b.d\"\n\nHere `f` represents a field in some root message, `a` and `b`\nfields in the message found in `f`, and `d` a field found in the\nmessage in `f.b`.\n\nField masks are used to specify a subset of fields that should be\nreturned by a get operation or modified by an update operation.\nField masks also have a custom JSON encoding (see below).\n\n# Field Masks in Projections\n\nWhen used in the context of a projection, a response message or\nsub-message is filtered by the API to only contain those fields as\nspecified in the mask. For example, if the mask in the previous\nexample is applied to a response message as follows:\n\n f {\n a : 22\n b {\n d : 1\n x : 2\n }\n y : 13\n }\n z: 8\n\nThe result will not contain specific values for fields x,y and z\n(their value will be set to the default, and omitted in proto text\noutput):\n\n\n f {\n a : 22\n b {\n d : 1\n }\n }\n\nA repeated field is not allowed except at the last position of a\npaths string.\n\nIf a FieldMask object is not present in a get operation, the\noperation applies to all fields (as if a FieldMask of all fields\nhad been specified).\n\nNote that a field mask does not necessarily apply to the\ntop-level response message. In case of a REST get operation, the\nfield mask applies directly to the response, but in case of a REST\nlist operation, the mask instead applies to each individual message\nin the returned resource list. In case of a REST custom method,\nother definitions may be used. Where the mask applies will be\nclearly documented together with its declaration in the API. In\nany case, the effect on the returned resource/resources is required\nbehavior for APIs.\n\n# Field Masks in Update Operations\n\nA field mask in update operations specifies which fields of the\ntargeted resource are going to be updated. The API is required\nto only change the values of the fields as specified in the mask\nand leave the others untouched. If a resource is passed in to\ndescribe the updated values, the API ignores the values of all\nfields not covered by the mask.\n\nIf a repeated field is specified for an update operation, new values will\nbe appended to the existing repeated field in the target resource. Note that\na repeated field is only allowed in the last position of a `paths` string.\n\nIf a sub-message is specified in the last position of the field mask for an\nupdate operation, then new value will be merged into the existing sub-message\nin the target resource.\n\nFor example, given the target message:\n\n f {\n b {\n d: 1\n x: 2\n }\n c: [1]\n }\n\nAnd an update message:\n\n f {\n b {\n d: 10\n }\n c: [2]\n }\n\nthen if the field mask is:\n\n paths: [\"f.b\", \"f.c\"]\n\nthen the result will be:\n\n f {\n b {\n d: 10\n x: 2\n }\n c: [1, 2]\n }\n\nAn implementation may provide options to override this default behavior for\nrepeated and message fields.\n\nIn order to reset a field's value to the default, the field must\nbe in the mask and set to the default value in the provided resource.\nHence, in order to reset all fields of a resource, provide a default\ninstance of the resource and set all fields in the mask, or do\nnot provide a mask as described below.\n\nIf a field mask is not present on update, the operation applies to\nall fields (as if a field mask of all fields has been specified).\nNote that in the presence of schema evolution, this may mean that\nfields the client does not know and has therefore not filled into\nthe request will be reset to their default. If this is unwanted\nbehavior, a specific service may require a client to always specify\na field mask, producing an error if not.\n\nAs with get operations, the location of the resource which\ndescribes the updated values in the request message depends on the\noperation kind. In any case, the effect of the field mask is\nrequired to be honored by the API.\n\n## Considerations for HTTP REST\n\nThe HTTP kind of an update operation which uses a field mask must\nbe set to PATCH instead of PUT in order to satisfy HTTP semantics\n(PUT must only be used for full updates).\n\n# JSON Encoding of Field Masks\n\nIn JSON, a field mask is encoded as a single string where paths are\nseparated by a comma. Fields name in each path are converted\nto/from lower-camel naming conventions.\n\nAs an example, consider the following message declarations:\n\n message Profile {\n User user = 1;\n Photo photo = 2;\n }\n message User {\n string display_name = 1;\n string address = 2;\n }\n\nIn proto a field mask for `Profile` may look as such:\n\n mask {\n paths: \"user.display_name\"\n paths: \"photo\"\n }\n\nIn JSON, the same mask is represented as below:\n\n {\n mask: \"user.displayName,photo\"\n }\n\n# Field Masks and Oneof Fields\n\nField masks treat fields in oneofs just as regular fields. Consider the\nfollowing message:\n\n message SampleMessage {\n oneof test_oneof {\n string name = 4;\n SubMessage sub_message = 9;\n }\n }\n\nThe field mask can be:\n\n mask {\n paths: \"name\"\n }\n\nOr:\n\n mask {\n paths: \"sub_message\"\n }\n\nNote that oneof type names (\"test_oneof\" in this case) cannot be used in\npaths.\n\n## Field Mask Verification\n\nThe implementation of any API method which has a FieldMask type field in the\nrequest should verify the included field paths, and return an\n`INVALID_ARGUMENT` error if any path is unmappable.", "type": "object", "title": "`FieldMask` represents a set of symbolic field paths, for example:", "properties": { "paths": { "description": "The set of field mask paths.", "type": "array", "items": { "type": "string" } } } }, "serviceAdditionalInfo": { "description": "Additional information for LookalikeDomainUpdateResponse. Used to support partial API updates.", "type": "object", "properties": { "message": { "type": "string", "readOnly": true } } }, "serviceDetectionOption": { "description": "The attribute is a key-value pair for optional values for user-created target domains.", "type": "object", "properties": { "name": { "description": "The name of the attribute", "type": "string" }, "value": { "description": "The value of the detector option.", "type": "string" } } }, "serviceGetLookalikeDomainsResponse": { "type": "object", "properties": { "results": { "type": "array", "items": { "$ref": "#/definitions/serviceLookalikeDomain" } } } }, "serviceItemStructs": { "description": "The Items structure that contains the item, its description, and its configuration settings.", "type": "object", "properties": { "description": { "description": "The description of the item.", "type": "string", "example": "Item description" }, "detection_options": { "description": "The detection options of the item.\nSld, Prefix, Embedding, ComboSquatting..", "type": "array", "items": { "$ref": "#/definitions/serviceDetectionOption" } }, "infoblox_suggested": { "description": "Determines whether this is a suggested target.", "type": "boolean", "format": "boolean" }, "item": { "description": "The data of the item.", "type": "string", "example": "example.com" }, "query_count_daily": { "description": "The number of times the target domain was queried from a specific account on the day of processing (previous day).", "type": "integer", "format": "int32", "readOnly": true }, "rejection_reason": { "description": "The reason for the rejection status of the target domain.", "type": "string", "readOnly": true, "example": "Watched domain is not resolvable" }, "selected": { "description": "Determines whether this candidate is selected.\nUsed only for target candidates.", "type": "boolean", "format": "boolean" }, "target_domain_status": { "description": "The status of the target domain.", "type": "string", "readOnly": true, "example": [ "accepted", "rejected", "submitted" ] }, "valid": { "description": "Is the item valid.", "type": "boolean", "format": "boolean" } } }, "serviceLookalikeCandidatesReadResponse": { "type": "object", "properties": { "results": { "description": "The Lookalike Target Domain List object that contains target candidates.", "$ref": "#/definitions/serviceTargetDomainsList" } } }, "serviceLookalikeCandidatesUpdateRequest": { "type": "object", "properties": { "account_specific": { "description": "Determines whether account-specific or common candidates are to be updated. The default value is \\\"false\\\": common candidates are to be returned.", "type": "boolean", "format": "boolean" }, "select": { "type": "array", "items": { "type": "string" } }, "unselect": { "type": "array", "items": { "type": "string" } } } }, "serviceLookalikeCandidatesUpdateResponse": { "type": "object" }, "serviceLookalikeDomain": { "description": "The Lookalike Domain object.\n\nThe Lookalike Domain object.", "type": "object", "properties": { "categories": { "description": "The list of categories this lookalike detection is related to.", "type": "array", "items": { "type": "string" }, "readOnly": true }, "lookalike_domain": { "description": "The lookalike domain.", "type": "string", "readOnly": true }, "lookalike_host": { "description": "The lookalike domain's FQDN.", "type": "string", "readOnly": true }, "malware": { "description": "Indicates whether the detected lookalike domain is malware.", "type": "boolean", "format": "boolean", "readOnly": true }, "phishing": { "description": "Indicates whether the detected lookalike domain is phishing.", "type": "boolean", "format": "boolean", "readOnly": true }, "reason": { "description": "The reason this domain looks like the target domain.", "type": "string", "readOnly": true }, "registration_date": { "description": "The date this lookalike was first registered.", "type": "string", "readOnly": true }, "suspicious": { "description": "Indicates whether the detected lookalike domain is suspicious.", "type": "boolean", "format": "boolean", "readOnly": true }, "target_domain": { "description": "The target domain this lookalike domain is associated to.", "type": "string", "readOnly": true }, "type": { "description": "The type of the domain: custom or common.", "type": "string" } } }, "serviceLookalikeDomainDetection": { "type": "object", "properties": { "detected_at": { "description": "The time this Lookalike Domain object was detected.", "type": "string", "format": "date-time", "readOnly": true }, "lookalike_domain": { "description": "The lookalike domain.", "type": "string", "readOnly": true }, "lookalike_host": { "description": "The lookalike domain's FQDN.", "type": "string", "readOnly": true }, "reason": { "description": "The reason this domain looks like the target domain.", "type": "string", "readOnly": true }, "suspicious": { "description": "Indicates whether the detected lookalike domain is suspicious.", "type": "boolean", "format": "boolean", "readOnly": true }, "target_domain": { "description": "The target domain this lookalike domain is associated to.", "type": "string", "readOnly": true } } }, "serviceLookalikeDomainReadMultiResponse": { "description": "The Lookalike Domain list response.", "type": "object", "properties": { "results": { "description": "The list of Lookalike Domain objects.", "type": "array", "items": { "$ref": "#/definitions/serviceLookalikeDomainDetection" } } } }, "serviceLookalikeDomainUpdateRequest": { "description": "The Lookalike Domain update request.", "type": "object", "properties": { "expose": { "type": "array", "items": { "type": "string" } }, "hide": { "type": "array", "items": { "type": "string" } } } }, "serviceLookalikeDomainUpdateResponse": { "description": "The Lookalike Domain update response.", "type": "object", "properties": { "additional_info": { "$ref": "#/definitions/serviceAdditionalInfo" } } }, "serviceLookalikeTargetsReadResponse": { "description": "The Lookalike Target Domain List read response.", "type": "object", "properties": { "results": { "description": "The Lookalike Target Domain List object that contains the target domain.", "$ref": "#/definitions/serviceTargetDomainsList" } } }, "serviceLookalikeTargetsUpdateRequest": { "description": "The Lookalike Target Domain create or update request.", "type": "object", "properties": { "fields": { "description": "Field Mask.", "$ref": "#/definitions/protobufFieldMask" }, "items": { "description": "The list of the FQDN or IPv4 addresses used to define allow-lists and deny-lists for additional protection.", "type": "array", "items": { "type": "string" }, "example": [ "example.com" ] }, "items_described": { "description": "The list of ItemStructs structures that contains items and their descriptions.", "type": "array", "items": { "$ref": "#/definitions/serviceItemStructs" } } } }, "serviceLookalikeTargetsUpdateResponse": { "description": "The Lookalike Target Domain create or update response.", "type": "object", "properties": { "success": { "properties": { "code": { "type": "string", "example": "UPDATED" }, "status": { "type": "integer", "format": "int32", "example": 201 } } } } }, "serviceTargetDomainsList": { "description": "The Target Domains List object.\n\nThe Target Domains List object holds all second-level domains used to target for lookalike domain detections.", "type": "object", "properties": { "created_time": { "description": "The time this List object was created.", "type": "string", "format": "date-time", "readOnly": true }, "description": { "description": "The brief description of the list. Always \"Auto-generated\".", "type": "string", "example": "Auto-generated" }, "id": { "description": "The List object's identifier.", "type": "integer", "format": "int32", "readOnly": true }, "item_count": { "description": "The number of items in this list.", "type": "integer", "format": "int32", "readOnly": true, "example": 8 }, "items": { "description": "The list of the SLDs used to define target domains for lookalike detection.", "type": "array", "items": { "type": "string" }, "example": [ "example.com" ] }, "items_described": { "description": "The list of ItemStructs structures that contains items and their descriptions.", "type": "array", "items": { "$ref": "#/definitions/serviceItemStructs" } }, "name": { "description": "The name of the list. Always \"Global Lookalike Target List\".", "type": "string", "example": "Global Lookalike Target List" }, "updated_time": { "description": "The time of this List object's most recent update.", "type": "string", "format": "date-time", "readOnly": true } } } } }