> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iotee.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Device management with REST endpoints and WebSocket realtime subscriptions.

## What you can do

<CardGroup cols={2}>
  <Card title="Manage Devices" icon="microchip">
    List, query, and monitor IoT devices.
  </Card>

  <Card title="Query Telemetry" icon="chart-line">
    Access GPS and battery history with time-range queries for any device.
  </Card>

  <Card title="Track Trips" icon="route">
    Compute trips and stops on-demand from GPS data with configurable motion detection.
  </Card>

  <Card title="Realtime Updates" icon="bolt">
    Subscribe to live device telemetry, status changes, and lock events via WebSocket.
  </Card>
</CardGroup>

## Access levels

The API uses API key authentication via the `X-API-Key` header. There are two roles:

| Role      | Access                                                                             |
| --------- | ---------------------------------------------------------------------------------- |
| **User**  | Devices, telemetry, lock events, trips, and WebSocket — scoped to assigned devices |
| **Admin** | Everything above (unrestricted) plus device management and user management         |

<Note>User accounts can only access devices assigned to them. This scoping applies to all endpoints including REST API, trips, lock events, and WebSocket subscriptions.</Note>

## Architecture

The Exchange API sits between your applications and IoT devices:

* **REST API** — Device queries, telemetry history, trip computation
* **WebSocket** — Realtime push of device data, status changes, and lock events

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Get up and running with your first API call in under 5 minutes.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/user/list-devices">
    Browse the full API reference for all available endpoints.
  </Card>
</CardGroup>