JavaScript Examples
Runnable Node.js examples for the KiloCenter gRPC API — install @grpc/grpc-js with dynamic proto loading, call methods.
This page provides runnable Node.js examples for the KiloCenter gRPC API using dynamic proto loading. For the full API reference, see API Reference.
For general Node.js gRPC documentation, see grpc.io/docs/languages/node.
Prerequisites
All commands in this guide assume your working directory is
kilocenter-modules/.
Install the gRPC and proto-loader packages:
npm install @grpc/grpc-js @grpc/proto-loaderNo stub generation is needed — @grpc/proto-loader loads .proto files at runtime. Ensure the proto files are accessible at the paths referenced below (relative to the KiloCenter repository root):
KC-Core/api/proto/kilocenter.protoKC-Core/api/proto/core.protoKC-Core/api/proto/identity.proto
Get System Status
Retrieves the current system status including version, uptime, and service health.
const grpc = require("@grpc/grpc-js");
const protoLoader = require("@grpc/proto-loader");
// KiloCenter KC-Gateway gRPC endpoint
const server = "localhost:9090";
const packageDef = protoLoader.loadSync("KC-Core/api/proto/kilocenter.proto", {
keepCase: false,
longs: String,
enums: String,
defaults: true,
oneofs: true,
includeDirs: ["KC-Core/api/proto"],
});
const proto = grpc.loadPackageDefinition(packageDef);
const client = new proto.kilocenter.api.v1.KiloCenterService(
server,
grpc.credentials.createInsecure()
);
client.GetSystemStatus({}, (err, resp) => {
if (err) {
console.error("GetSystemStatus failed:", err.message);
process.exit(1);
}
console.log("Version: ", resp.version);
console.log("Status: ", resp.status);
console.log("Uptime: ", resp.uptime);
console.log("Active Endpoints: ", resp.activeEndpoints);
console.log("Active Base Stations:", resp.activeBasestations);
console.log("Messages Processed: ", resp.messagesProcessed);
for (const svc of resp.services) {
console.log(` Service: ${svc.name} healthy=${svc.healthy} latency=${svc.latencyMs}ms`);
}
});List Endpoints
Lists registered endpoints with pagination support. High-volume profile: default page size 100, max 1000.
Authentication
Community Edition
Community Edition runs in single-tenant mode with authentication and organization enforcement disabled (auth.enabled: false, org_enforcement_enabled: false). The examples above work without any headers.
Enterprise: JWT User Principal
Requires three headers: authorization, x-organization-id, and x-user-id. The x-user-id value must match the authenticated user in the JWT. Missing x-user-id returns ErrTokenUserIDHeaderRequired; a mismatch returns ErrTokenIdentityMismatch.
Enterprise: Service-Account API Key
Requires two headers: authorization and x-organization-id. Do not send x-user-id — including it returns ErrTokenIdentityMismatch to prevent user injection.
Last updated