> 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/espanol/api-skyone-autosky/api-de-autenticacion.md).

# API de Autenticación

Al obtener su token de autenticación para las llamadas de API de la plataforma Autosky, este token deberá ser utilizado en todas las llamadas de API.

Existen dos formas de utilizar el token de autenticación:

## Token vía URL

En esta modalidad, el token debe enviarse como argumento en las llamadas de la API.

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

## Token vía Header

En la modalidad de envío del token vía header, este debe pasarse como encabezado en las llamadas de la API.\
​\
El encabezado debe seguir el siguiente modelo:

```
Authorization: xxxxxx
```

**Ejemplo utilizando HTTPie:**

```bash
http https://meudominio.skyinone.net/v2/api/clients/ Authorization:xxxx
```

**Ejemplo utilizando cURL:**

```bash
curl -H "Authorization: xxxx" https://meudominio.skyinone.net/v2/api/clients/
```


---

# 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/espanol/api-skyone-autosky/api-de-autenticacion.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.