> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/iot-logic-api/authentication.md).

# Authentication

IoT Logic uses your Navixy Platform credential. Which credential type to use, and how to send it with a request.

IoT Logic runs on the Navixy platform, so it authenticates with the same credential as the rest of the Platform API: a user session hash or an API key. If you already have one, there is nothing IoT Logic specific to set up. Reuse it here.

## Which credential to use

Use an API key for IoT Logic work. Flows run unattended, and an API key does not expire, unlike a session hash. See [Platform authentication](/docs/navixy-api/user-api/authentication.md) for how the two credential types differ, how to obtain a session hash, and how to create an API key from the web interface.

To list, create, or delete API keys through the API itself, see [API keys](/docs/navixy-api/user-api/resources/commons/api-keys.md). Those operations need a standard session hash: an API key cannot manage API keys.

## Sending the credential

Send the credential in the `Authorization` header, after `NVX` and a space:

```bash
curl --request GET \
  --url 'https://api.eu.navixy.com/v2/iot/logic/flow/list' \
  --header 'Authorization: NVX your_hash_or_api_key'
```

A credential can also be sent in the request body or as a query parameter. See [Platform authentication](/docs/navixy-api/user-api/authentication.md) for both forms, and when each one is appropriate.

## Authentication errors

Authentication errors use the same codes across the platform, including IoT Logic. See [Errors](/docs/navixy-api/general/errors.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://navixy.com/docs/iot-logic-api/authentication.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.