Summary

The addIngestTokenV3() mutation creates a new ingest token for a LogScale repository. Ingest tokens authenticate data ingestion requests to a specific repository. You can assign a parser at creation time so that all events ingested with the token pass through that parser on arrival. Alternatively, you can supply a custom token string rather than accept the system-generated value; this requires root-level permissions.

API Stability Long-Term

Syntax

graphql
addIngestTokenV3(
      input: AddIngestTokenV3Input!
   ): IngestToken!

The mutation accepts a single required input argument of type AddIngestTokenV3Input!. The input requires the repository name and the new token name. The parser name and custom token string are optional. The mutation returns an IngestToken! object for the newly created token.

Example

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

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 {
  addIngestTokenV3(input: {
       repositoryName: \"humio\", 
       name: \"tokener1\"} )
     { name, token, parser { id, name, displayName} }
}"
}
);


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": {
    "addIngestTokenV3": {
      "name": "tokener1",
      "token": "abc123-def456-ghi789",
      "parser": {
          "id": "abc123",
          "name": "parser1",
          "displayName": "Main Parser"
        }
    }
  }
}

Input Parameters

Provide the repository name and the name for the new ingest token. Optionally, assign a parser at creation time or supply a custom token string.

Table: AddIngestTokenV3Input 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 
customTokenString  Long-Term A specific string to use as the token value instead of the system-generated value. Use this when you need a predictable token value, such as when migrating tokens from another system or managing token values through an external secrets manager. Requires root-level permissions. If omitted, LogScale generates the token value automatically.
nameStringyes Long-Term A name that identifies this token in the LogScale UI and API responses. Choose a name that reflects the data source or ingestion pipeline using the token.
parserString  Long-Term The name or identifier of the parser to assign to this token. All events ingested with this token pass through the specified parser on arrival. For parsers in packages, use the format packagescope/packagename:parsername. If omitted, events are stored without parser processing and the returned parser field is null.
repositoryNameStringyes Long-Term The name of the repository where the ingest token is created. The token authenticates data ingestion to this repository only.

Returned Values

The mutation returns an IngestToken! object for the newly created token. Request token to obtain the token string to use in Authorization: Bearer headers for data ingestion requests. The parser field returns the assigned parser object, or null if no parser was assigned at creation time.

Table: IngestToken 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 
nameStringyes Long-Term The name of the ingest token, as displayed in the LogScale UI and API responses.
parserParser  Long-Term The parser assigned to this token. All events ingested with this token pass through this parser on arrival. Returns null if no parser is assigned. See Parser.
tokenStringyes Long-Term The token string used to authenticate data ingestion requests. Include this value in the Authorization: Bearer header when sending events to LogScale.