# Getting started

## First steps

{% hint style="warning" %}
Before you can utilize data for comprehensive analytics and integration, you must first enable **IoT Query**. If you don't have it yet, contact us for enablement details - <iotquery@navixy.com>
{% endhint %}

Once it's set up, you'll receive a welcome email containing detailed information. To begin your data journey, you will need:

* Database host and port
* Database name
* Username and password
* SSL mode settings

{% hint style="info" %}
If you are not administering your Platform accounts yourself, contact your [GPS / Telematics service provider](/docs/user/guide/quick-start/about-service-providers.md) for access to **IoT Query**.
{% endhint %}

From there, your path forward is straight:

1. [Set up your connection](/docs/analytics/iot-query/connection-setup.md)\
   Configure your SQL client or analytics tool
2. [Explore data schemas](/docs/analytics/iot-query/schema-overview.md)\
   Discover the tables and relationships in your data
3. [Check SQL example queries](/docs/analytics/example-queries.md)\
   Use ready-made queries from our comprehensive recipe collection

We also recommend familiarizing yourself with [Data types and field standards](#data-types-and-field-standards) and [Important considerations](#important-considerations) before proceeding.

## Data types and field standards

**IoT Query** uses consistent data type conventions that may differ from the source systems:

* **Date and time fields** use the `TIMESTAMP` format
* **Text fields** use `CHARACTER VARYING` or `TEXT` types
* **ID fields** follow a consistent naming pattern with their table prefix (e.g., \`user\_id\`, \`device\_id\`)
* **Boolean fields** use prefixes like `is_`, `has_`, or `can_` (e.g., `is_active`, `has_passport`)

## Important considerations

While working with the **IoT Query**, be aware of these current limitations:

* **Error messaging** is minimal for SQL query issues
* **Transformation and Insight layers** are still in development and not available yet
* **Historical data** availability depends on your Platform subscription plan

For detailed information on structure and capability, see [Schema overview](/docs/analytics/iot-query/schema-overview.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/analytics/iot-query/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.