> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/integrations-and-extensions/cloud-api.md).

# Cloud API

Aranet Cloud API allows access to the sensor and cloud data outside of the Aranet ecosystem. Cloud API is a Pull-type integration. By using the Aranet Cloud API, Aranet Cloud can be integrated with any other web or cloud-based IT system or used as a data source for 3rd-party applications. 

**The main features of Aranet Cloud API:**

* Centralized  data  access  for  all  the  necessary sensors via a single connection 
* Pull-type API integration providing access to data in Aranet Cloud 
* On-demand data access from Aranet Cloud without the need to establish data storage on a 3rd-party IT system  
* Ability  to  request  current,  latest,  and  specified period data  
* Access to cloud-specific data like virtual sensors, alarms, assets 
* Authorization using API key 
* **API  documentation**  –  all  currently  available endpoints are documented via[ ](https://aranet.cloud/openapi/)[**Swagger**](https://aranet.cloud/openapi/) 
* Supported data format: JSON  

Currently implemented **Aranet Cloud API**:

* supports only GET requests, meaning that the 3rd-party system shall not be able to insert or update any data into the Aranet Cloud database;
* following data can be requested:
  * sensor measurements  (with UTC timestamps)
  * sensor list with sensor details (name, interval, sensorID, type)

**API key**:

* Each 3rd-party system receives its own API key, which is used to authenticate data requests.
* One API key authenticates to only one Aranet Cloud workspace.
* By default, the API key has the same units configuration as the user who creates it. 
* A key value must be 32 characters long.


---

# 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://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/integrations-and-extensions/cloud-api.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.