> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/kilo-mioty-service-center/integrations/grpc-first-steps.md).

# 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](/kilo-mioty-service-center/getting-started/configuration-basics.md) 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

```bash
grpcurl -plaintext localhost:9090 list
```

### Inspect Main Service

```bash
grpcurl -plaintext localhost:9090 describe kilocenter.api.v1.KiloCenterService
```

### Check gRPC Health Service

```bash
grpcurl -plaintext localhost:9090 grpc.health.v1.Health/Check
```

### Call a Basic API Method

```bash
grpcurl -plaintext -d '{}' \
  localhost:9090 kilocenter.api.v1.KiloCenterService/GetSystemStatus
```

### Authentication 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:

```bash
grpcurl -plaintext \
  -H "authorization: Bearer <JWT_TOKEN>" \
  -H "x-organization-id: <ORG_ID>" \
  -d '{}' \
  localhost:9090 kilocenter.api.v1.KiloCenterService/GetSystemStatus
```

### Next Step

Use the full API reference for request/response contracts:

* `kilocenter-modules/docs/api.md`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kiloiot.io/kilo-mioty-service-center/integrations/grpc-first-steps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.