canonical: https://jentic.com/apis/swaggerhub.qsi-swagger/api-atendente-web

# Qsi Swagger API Atendente Web

API REST para o sistema de Atendimento Attendance da Energisa. Autenticação 1. Configure 4 credenciais no botão Authorize 2. Chame POST /token para obter access_token 3. Use o token JWT nos demais endpoints. The API exposes 22 endpoints secured with basic, bearer authentication.

## For AI agents

Programmatically gerar token de acesso, informações do usuário logado. Covers 22 operations with basic, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Gerar token de acesso
- Informações do usuário logado
- Associar mesa ao atendente
- Realizar logout
- Alterar senha do usuário
- Configurações do Attendance
- Adicionar serviço ao atendimento

## Use cases

### Identity and Authentication Operations

Use the API Atendente Web to perform identity auth operations programmatically. The API provides 22 endpoints covering core functionality including gerar token de acesso, informações do usuário logado, associar mesa ao atendente.

Example prompt: Call POST /token to gerar token de acesso

### Automated Autenticação Management

Automate autenticação operations by combining multiple API Atendente Web endpoints. Agents can informações do usuário logado and then associar mesa ao atendente in a single workflow.

Example prompt: Call GET /me to informações do usuário logado, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Atendente Web 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 'gerar token de acesso', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /token | Gerar token de acesso |
| GET | /me | Informações do usuário logado |
| POST | /associar-mesa | Associar mesa ao atendente |
| POST | /logout | Realizar logout |
| POST | /alterar-senha | Alterar senha do usuário |
| GET | /configs-attendance | Configurações do Attendance |
| POST | /adicionar-servico | Adicionar serviço ao atendimento |
| POST | /alterar-servico | Alterar serviço do atendimento |

## Key resources

- **Autenticação** — Endpoints para autenticação e autorização
- **Atendimento** — Endpoints relacionados aos atendimentos
- **Atendente** — Endpoints relacionados aos atendentes

## Why Jentic

- **Setup:** Wiring API Atendente Web by hand means handling both its basic login and the JWT bearer token it issues, choosing the right atendimento.ai host, and coding retries yourself. Through Jentic you install once, import API Atendente Web from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** API Atendente Web carries its targets in the request body, not in the URL path, so you limit the agent to the operations it needs, such as fetching the attendant profile or reading attendance configs, 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 Atendente Web 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 'authenticate an attendant' or 'read the attendance configuration', and Jentic returns the matching API Atendente Web operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the API Atendente Web use?

The API Atendente Web 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 gerar token de acesso with the API Atendente Web?

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 Atendente Web?

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 gerar token de acesso through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gerar token de acesso'. Jentic returns the matching API Atendente Web operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Atendente Web have?

The API Atendente Web exposes 22 endpoints covering autenticação, atendimento, atendente operations.

### Can I limit what my agent is allowed to do with the API Atendente Web?

Yes. Because you run Jentic One yourself, your own rules decide which API Atendente Web operations and credentials the agent may use. Since this API carries its targets in the request body rather than the URL path, you can allow only the calls the agent actually needs, such as reading the logged-in attendant profile via GET /me or reading attendance settings via GET /configs-attendance, and leave out sensitive operations like POST /logout or POST /alterar-senha unless you choose to add them. Every operation the agent can call is one you explicitly allowed.