Summary

The deleteIPFilter() mutation permanently removes an IP filter from LogScale. IP filters define allowlists or blocklists of IP addresses and ranges that control inbound access to LogScale. Deleting a filter takes effect immediately — the filter's access rules stop applying at once, and the deletion cannot be undone. Before calling this mutation, use the ipFilters() query to retrieve the filter's unique identifier.

API Stability Long-Term

Syntax

graphql
deleteIPFilter(
      input: IPFilterIdInput!
   ): Boolean!

The mutation takes one required argument: input, an IPFilterIdInput object that supplies the unique identifier of the IP filter to delete. The IPFilterIdInput type contains a single field, id, which must match an existing filter identifier. The mutation returns Boolean! — true if the filter was deleted successfully, false if the deletion did not complete.

Example

Raw
graphql
mutation {
  deleteIPFilter(
    input: { id: "abc123" } 
  )
}
Mac OS or Linux (curl)
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}"
}
EOF
Mac OS or Linux (curl) One-line
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}"
}
EOF
Windows Cmd and curl
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql ^
    -H "Authorization: Bearer $TOKEN" ^
    -H "Content-Type: application/json" ^
    -d @'{"query" : "mutation { ^
  deleteIPFilter( ^
    input: { id: \"abc123\" }  ^
  ) ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}"
}'
    "$YOUR_LOGSCALE_URL/graphql"
Perl
perl
#!/usr/bin/perl

use HTTP::Request;
use LWP;

my $TOKEN = "TOKEN";

my $uri = '$YOUR_LOGSCALE_URL/graphql';

my $query = "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}";
$query =~ s/\n/ /g;
my $json = sprintf('{"query" : "%s"}',$query);
my $req = HTTP::Request->new("POST", $uri );

$req->header("Authorization" => "Bearer $TOKEN");
$req->header("Content-Type" => "application/json");

$req->content( $json );

my $lwp = LWP::UserAgent->new;

my $result = $lwp->request( $req );

print $result->{"_content"},"\n";
Python
python
#! /usr/local/bin/python3

import requests

url = '$YOUR_LOGSCALE_URL/graphql'
mydata = r'''{"query" : "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}"
}'''

resp = requests.post(url,
                     data = mydata,
                     headers = {
   "Authorization" : "Bearer $TOKEN",
   "Content-Type" : "application/json"
}
)

print(resp.text)
Node.js
javascript
const https = require('https');

const data = JSON.stringify(
    {"query" : "mutation {
  deleteIPFilter(
    input: { id: \"abc123\" } 
  )
}"
}
);


const options = {
  hostname: '$YOUR_LOGSCALE_URL',
  path: 'graphql',
  port: 443,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Content-Length': data.length,
    Authorization: 'BEARER ' + process.env.TOKEN,
    'User-Agent': 'Node',
  },
};

const req = https.request(options, (res) => {
  let data = '';
  console.log(`statusCode: ${res.statusCode}`);

  res.on('data', (d) => {
    data += d;
  });
  res.on('end', () => {
    console.log(JSON.parse(data).data);
  });
});

req.on('error', (error) => {
  console.error(error);
});

req.write(data);
req.end();
Example Responses
Success (HTTP Response Code 200 OK)
json
{
  "data": {
    "deleteIPFilter": true
  }
}

Input Parameters

The input argument requires an IPFilterIdInput object that identifies the filter to delete. Use the ipFilters() query to retrieve filter identifiers before calling this mutation. The following table describes the IPFilterIdInput fields:

Table: IPFilterIdInput Input Datatype

ParameterTypeRequiredDefaultStabilityAvailabilityDescription
Some input parameters may be required, as indicated in the Required column. For return values, this indicates that you are assured a value if the field is requested for the results. 
Table last updated: Oct 14, 2026 
idStringyes Long-Term The unique identifier of the IP filter.