> 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/api/examples.md).

# Examples

Authentication examples for the Kilo IoT API — curl REST and gRPC headers using X-API-Key and X-Organization-Id.

These examples show how to authenticate. For the operations themselves, see the [API reference](https://api.kiloiot.io/).

## Authenticated REST request

Replace the placeholders with your key and organization ID:

```bash
curl -sS https://api.kiloiot.io/api/v2/devices \
  -H "X-API-Key: $KILO_API_KEY" \
  -H "X-Organization-Id: $KILO_ORG_ID"
```

`GET /api/v2/devices` returns the devices the key is allowed to see (it requires a Devices **Read** scope). Use the same two headers for other calls; check the API reference for the path and the scope each one needs.

## gRPC

gRPC uses the same headers. For native gRPC client definitions, use the materials provided with your on-premise or integration package.

## Good practice

* Keep the key in an environment variable or secret store — never in shell history or source control.
* Use a dedicated key per integration with only the scopes it needs.
* See [Authentication & API keys](/api/authentication-and-api-keys.md) for the full guidance.


---

# 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/api/examples.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.