Since an ingest token can be associated with more than one parser, you may decide to no longer allow access to a parser with a particular ingest token. To disassociate a parser and ingest token, use the unassignIngestToken() GraphQL mutation.

To associate a parser with an ingest token, use the assignParserToIngestTokenV2() mutation. To add a new ingest token, use the addIngestTokenV3() mutation. To delete an ingest token, use removeIngestToken().

Hide Query Example

Show Ingest Tokens Query

To change the parser associated with an ingest token using the LogScale UI, see the Assign a Parser to a Token section of the Ingest Tokens documentation page.

API Stability Long-Term

Syntax

graphql
unassignIngestToken(
     repositoryName: string!,
     tokenName: string!
   ): UnassignIngestTokenMutation!

For the input, you have to provide the name of the repository and the token to unassign from it.

For the results, you can get information on the repository associated with the ingest token. See the Returned Datatype section for more.

Example

Raw
graphql
mutation {
  unassignIngestToken(
    repositoryName: "humio",
    tokenName: "my-token"
  )
  { repository { name } }
}
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 {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}"
}
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 {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}"
}
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 { ^
  unassignIngestToken( ^
    repositoryName: \"humio\", ^
    tokenName: \"my-token\" ^
  ) ^
  { repository { name } } ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}"
}'
    "$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 {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}";
$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 {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}"
}'''

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 {
  unassignIngestToken(
    repositoryName: \"humio\",
    tokenName: \"my-token\"
  )
  { repository { name } }
}"
}
);


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": {
    "unassignIngestToken": {
      "repository": {
        "name": "humio"
      }
    }
  }
}

Given Datatype

For the input, you have to provide the name of the repository and the token to unassign from it.

Table: Input Using Standard Datatypes

Parameter Type Required Default Description
repositoryName string yes   The name of the repository.
tokenName string yes   The name of the ingest token to unassign.

Returned Datatype

The returned datatype, through sub-parameters, allows you to get information on a repository associated with the ingest token. The table below provides a link to a table with these sub-parameters:

Table: UnassignIngestTokenMutation

ParameterTypeRequiredDefaultStabilityDescription
Some arguments may be required, as indicated in the Required column. For return datatypes, this indicates that you must specify which fields you want returned in the results.
Table last updated: Oct 4, 2024
repositoryRepositoryyes Long-TermThe repository for the unassigned token mutation. See Repository.