Qsi Swagger API Attendance Energisa
Browse all Swaggerhub Qsi Swagger APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic, bearer28 EndpointsREST
For 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.
Use for: I need to realiza a autenticação na api do attendance, I want to associa uma mesa de uma unidade ao usuário logado, Search for realiza o logout do atendente, Find all lista as unidades permitidas para o usuário logado
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Api simplificada para o módulo de atendimento do Attendance. The API exposes 28 endpoints secured with basic, bearer authentication.
Install Jentic One Beta
Connect the API Attendance Energisa to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Attendance Energisa, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API Attendance Energisa API.
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
Patterns agents use API Attendance Energisa API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'realiza a autenticação na api do attendance', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
28 endpoints — api simplificada para o módulo de atendimento do attendance.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Attendance Energisa basic, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'realiza a autenticação na api do attendance') and Jentic returns the matching API Attendance Energisa operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Attendance Energisa integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using API Attendance Energisa API through Jentic.
What authentication does the API Attendance Energisa use?
The API Attendance Energisa uses basic, bearer authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED