> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/api-skyone-autosky/introduction.md).

# Introduction

This documentation presents the information required to integrate systems and platforms with the **Skyone Autosky API**. 

Through this API, it will be possible to perform integration procedures with the following objects:

* **Clients (User Groups)**
* **Users**
* **Applications**
* **User Sessions**
* **User Authentication**
* **User Logon**

### Version

V2.3 - (07/19/2024)

### Prerequisites

To use the APIs, you must have access to the authentication information provided by the Skyone integration team.

For Example:

| Item                 | Example                                |
| -------------------- | -------------------------------------- |
| Authentication Token | `23a1e4e6f90546e498a8f66cf21e3fb3`     |
| Environment UUID     | `6a6c7a07-bef1-4e42-942e-87277a8c2a84` |
| Staging URL          | `piloto.skyinone.net`                  |
| Production URL       | `meudominio.skyinone.net`              |

## URL Base 

```
https://meudominio.skyinone.net/v2/api/
```

### API Call Authentication

Once you obtain your authentication token for the Autosky platform API calls, this token must be used in all API requests. There are two ways to use the authentication token:

### Token via URL

In this method, the token must be sent as a query parameter in the API calls, for example:

`http://meudominio.skyinone.net/v2/api/clients/`**`?token=xxxxx`**

#### Token via Header

When sending the token via header, it must be passed as a header in the API calls. The header must follow this format:

* **Authorization:xxxxxx**

In this example using HTTPie: http <http://meudominio.skyinone.net/v2/api/clients/>  **Authorization:xxxx**


---

# 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 dynamically by asking a question.

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

```
GET https://docs.skyone.cloud/english/api-skyone-autosky/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.