canonical: https://jentic.com/apis/swaggerhub.qsi-swagger/api-attendance-energisa

# Qsi Swagger API Attendance Energisa

API simplificada para o módulo de atendimento do Attendance. The API exposes 28 endpoints secured with basic, bearer authentication.

## For AI agents

Programmatically realiza a autenticação na API do attendance, associa uma mesa de uma unidade ao usuário logado. Covers 28 operations with basic, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Realiza a autenticação na API do Attendance
- Associa uma mesa de uma unidade ao usuário logado
- Lista as unidades permitidas para o usuário logado
- Obter dados da entidade logada
- Monitor API Attendance Energisa operational status and events

## Use cases

### Developer Tools Operations

Use the API Attendance Energisa to perform developer tools operations programmatically. The API provides 28 endpoints covering core functionality including realiza a autenticação na API do attendance, associa uma mesa de uma unidade ao usuário logado, realiza o logout do atendente.

Example prompt: Call POST /token to realiza a autenticação na API do attendance

### Automated Autenticação Management

Automate autenticação operations by combining multiple API Attendance Energisa endpoints. Agents can associa uma mesa de uma unidade ao usuário logado and then realiza o logout do atendente in a single workflow.

Example prompt: Call POST /associar-mesa to associa uma mesa de uma unidade ao usuário logado, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Attendance Energisa endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, bearer tokens manually.

Example prompt: Search Jentic for 'realiza a autenticação na API do attendance', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /token | Realiza a autenticação na API do Attendance |
| POST | /associar-mesa | Associa uma mesa de uma unidade ao usuário logado |
| POST | /logout | Realiza o logout do atendente |
| GET | /unidades-permitidas | Lista as unidades permitidas para o usuário logado |
| GET | /setores-unidade | Lista os setores de uma unidade |
| GET | /mesas-atendimento-disponiveis | Lista as mesas de atendimento disponíveis |
| GET | /me | Obter dados da entidade logada |
| POST | /alterar-senha | Alterar senha do usuário |

## Key resources

- **Autenticação** — Endpoints de autenticação e gestão de sessão
- **Atendimento** — Endpoints relacionados ao fluxo de atendimento
- **Totem** — Endpoints específicos para operação via totem de autoatendimento
- **Painel** — Endpoints relacionados ao painel de atendimento
- **Configuração** — Endpoints de configuração e consulta de dados

## Why Jentic

- **Setup:** Wiring API Attendance Energisa by hand means handling its basic login plus the JWT bearer token it returns, pointing at its api-gateway.atendimento.ai host, and coding retries yourself. Through Jentic you install once, import API Attendance Energisa from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** API Attendance Energisa carries its targets in the request body, not in the URL path, so you limit the agent to the operations it needs, such as listing permitted units or available service desks, and leave out logout or password change unless you add them. Every operation the agent can call is one you chose to allow.
- **Credential handling:** Your API Attendance Energisa credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list permitted units' or 'list available service desks', and Jentic returns the matching API Attendance Energisa operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API Attendance Energisa use?

The API Attendance Energisa uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I realiza a autenticação na API do attendance with the API Attendance Energisa?

Yes. Use the POST /token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Attendance Energisa?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I realiza a autenticação na API do attendance through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'realiza a autenticação na API do attendance'. Jentic returns the matching API Attendance Energisa operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Attendance Energisa have?

The API Attendance Energisa exposes 28 endpoints covering autenticação, atendimento, totem operations.

### Can I limit what my agent is allowed to do with the API Attendance Energisa?

Yes. Jentic One runs self-hosted, so your own rules decide which API Attendance Energisa operations and credentials the agent may use. Because this API carries its targets in the request body rather than the URL path, you can allow only the read operations the agent needs, such as GET /unidades-permitidas to list permitted units or GET /mesas-atendimento-disponiveis to list available service desks, while withholding POST /logout or POST /alterar-senha. Every operation the agent can call is one you chose to allow.