Qsi Swagger API Atendente Web

Name: API Atendente Web API
Brand: API Atendente Web
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthorizationbasic, bearer22 Endpoints

Install Jentic One Beta

Connect the API Atendente Web to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Atendente Web, 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.

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 | sh

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 instance

Jentic 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 Atendente Web API.

Gerar token de acesso

Informações do usuário logado

Associar mesa ao atendente

Realizar logout

GET STARTED

Start building with API Atendente Web API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to gerar token de acesso, I want to informações do usuário logado, Search for associar mesa ao atendente, Find all realizar logout

Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.

Use Cases

Patterns agents use API Atendente Web API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'gerar token de acesso', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

22 endpoints — api rest para o sistema de atendimento attendance da energisa.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

API Atendente Web 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., 'gerar token de acesso') and Jentic returns the matching API Atendente Web operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Atendente Web integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using API Atendente Web API through Jentic.

What authentication does the API Atendente Web use?

The API Atendente Web 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 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 at https://app.jentic.com/sign-up, 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.

Qsi Swagger API Atendente Web

Connect the API Atendente Web to your agent

Capabilities

Start building with API Atendente Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs