Endpoint

/3.0/dnsbl

Description

Update or create a new entry in the DNS Blacklist.

...

Just as in the regular lookup case DNSBLv5APIv3: getListed (POST). However, be

Multiple entries in the same input

Be careful with the variant described at the other doc here. Putting data into the system DO do support multiple addresses. This however, changes the requirements of the input data object. In the old API, adding data without a bitmasked value would set the bitmask value 64 to the host (IP_ABUSE_NO_SMTP). In the APIv3 service this kind of syntax is empty bitmasks on multiple hosts are not allowed, since we prefer to get proper bitmask values on each added host (in case they are different to each other). So, this does not work:

{
    "ip":["44.11.12.77","18.33.14.30"]
}

This is what happens in such cases:

{
    "response": [],
    "errors": {
        "code": "400",
        "success": "",
        "faultstring": "Updating or adding multiple entries requires a syntax with associative arrays (arrays with keys)"
    }
}

How do the requests look then?

To be more specific with what kind of address you're adding, you can also format your input syntax like this:

...

{
	"dnsblResponse": {
		"status": [{
				"address": "44.11.12.77",
				"arpa": "77.12.11.44",
				"state": "new",
				"arpaDelegations": [
					"77.12.11.44.dnsbl.tornevall.org"
				],
				"flag": "32"
			},
			{
				"address": "18.33.14.30",
				"arpa": "30.14.33.18",
				"state": "new",
				"arpaDelegations": [
					"30.14.33.18.dnsbl.tornevall.org",
					"30.14.33.18.bl.fraudbl.org"
				],
				"flag": "99102"
			}
		]
	}
}