Stability Level Preview
API Stability Preview

The createRemoteTableConfig() GraphQL mutation is used to create a remote table configuration.

Syntax

Below is the syntax for the createRemoteTableConfig() mutation field:

graphql
createRemoteTableConfig(
      input: CreateOrUpdateRemoteTableConfigInput!
   ): RemoteTableConfig!

Below is an example of how this mutation field might be used:

Raw
graphql
mutation {
  createRemoteTableConfig(
    input: { 
      connectionName: "some-table",
      connectionDescription: "Some Table"
    }
  ) { connectionName }
}
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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}
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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}
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 { ^
  createRemoteTableConfig( ^
    input: {  ^
      connectionName: \"some-table\", ^
      connectionDescription: \"Some Table\" ^
    } ^
  ) { connectionName } ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}'
    "$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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}";
$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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}'''

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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}
);


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": {
    "createRemoteTableConfig": {
      "connectionName": "some-table"
    }
  }
}

Given Datatypes

For the CreateOrUpdateRemoteTableConfigInput given datatype, there are a few parameters. Below is a list of them, along with a description of each.

Table: CreateOrUpdateRemoteTableConfigInput

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: Dec 17, 2025
connectionConfigGenericGenericConnectionConfigInput  PreviewThe configuration of a generic remote table. See GenericConnectionConfigInput.
connectionDescriptionstringyes PreviewThe description of the remote table configuration.
connectionNamestringyes PreviewThe name of the remote table configuration. This must be unique in the organization.

Returned Datatypes

For RemoteTableConfig, there are several parameters that may be requested. Below is a list of them:

Table: RemoteTableConfig

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: Dec 16, 2025
connectionConfigRemoteTableConnectionConfigyes PreviewThe configuration of the remote table connection. See RemoteTableConnectionConfig.
connectionDescriptionstringyes PreviewThe description of the remote table configuration.
connectionNamestringyes PreviewThe name of the remote table connection.