gRPC First Steps
Check KiloCenter gRPC access through the local API gateway with grpcurl, discover methods, and supply authentication when enabled.
Use KiloCenter's gRPC API to make MIOTY network operations part of your software: manage endpoints, request downlinks, and inspect their results. gRPC provides defined operations with structured request and response messages, so you can build an integration around the service center's contract.
The examples below use grpcurl, a command-line client, to exercise that interface before writing application code.
The commands below use the local API entry point at localhost:9090, exposed by KC-Gateway. Have the stack running and check its port configuration first. These examples use a local plaintext connection; authentication and transport settings must match the installation you are calling.
What does this guide achieve?
Verify local gRPC connectivity through KC-Gateway and discover the KiloCenterService methods.
Check Service Reachability
grpcurl -plaintext localhost:9090 listInspect Main Service
grpcurl -plaintext localhost:9090 describe kilocenter.api.v1.KiloCenterServiceCheck gRPC Health Service
grpcurl -plaintext localhost:9090 grpc.health.v1.Health/CheckCall a Basic API Method
grpcurl -plaintext -d '{}' \
localhost:9090 kilocenter.api.v1.KiloCenterService/GetSystemStatusAuthentication and Organization Context
The current Community Edition Docker configuration enables local sign-in in KC-Identity and token validation in KC-Gateway. Authenticate protected API calls through the gateway. The examples omit installation-specific credentials; they do not mean that authentication should be disabled. Keep internal service ports private.
If you enable authentication (Enterprise Edition or by setting KILOCENTER_AUTH_ENABLED=true), include metadata headers in gRPC calls:
Next Step
Use the full API reference for request/response contracts:
kilocenter-modules/docs/api.md
Last updated