removed
Breaking change - Deleting targets
12 days ago by Mike Jarrett
When deleting a target, we previously would respond with HTTP 204 No Content with the response body of the string "Target has been deleted successfully.".
We no longer return this string an instead return no conent in the response body. The returned HTTP status remains the same of HTTP 204 No Content.
$ curl "https://api.intruder.io/v1/targets/$id/" \
-X DELETE \
-H "Authorization: Bearer $apiKey" \
-v
* Host api.intruder.io:443 was resolved.
* IPv6: (none)
* IPv4: 104.22.45.110, 172.67.26.224, 104.22.44.110
* Trying 104.22.45.110:443...
* Connected to api.intruder.io (104.22.45.110) port 443
...
> GET /v1/targets/$id HTTP/2
> Host: api.intruder.io
> User-Agent: curl/8.7.1
> Accept: */*
> Authorization: Bearer $apiKey
>
* Request completely sent off
< HTTP/2 204 No content
< Date: Mon, 19 May 2025 13:14:00 GMT
< content-type: application/json
< allow: DELETE, OPTIONS
< content-length: 21
< x-frame-options: DENY
< x-content-type-options: nosniff
< referrer-policy: same-origin
< cross-origin-opener-policy: same-origin
<
* Connection #0 to host api.intruder.io left intact
$