Qsi Swagger AgendamentoAPI
Browse all Swaggerhub Qsi Swagger APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey14 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically gerar token de acesso, listar serviços disponíveis. Covers 14 operations with apiKey authentication.
Use for: I need to gerar token de acesso, I want to listar serviços disponíveis, Search for listar unidades diponíveis para o serviço, Find all insere ou atualiza um cliente
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Documentação da API para o agendamento do sistema Attendance. The API exposes 14 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the AgendamentoAPI to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AgendamentoAPI, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.qsi-swagger%2Fagendamentoapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.qsi-swagger%2Fagendamentoapi" | 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 AgendamentoAPI API.
Gerar token de acesso
Listar serviços disponíveis
Insere ou atualiza um cliente
Pesquisar cliente por número
Monitor AgendamentoAPI operational status and events
Use Cases
Patterns agents use AgendamentoAPI API for, with concrete tasks.
★ Developer Tools Operations
Use the AgendamentoAPI to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including gerar token de acesso, listar serviços disponíveis, listar unidades diponíveis para o serviço.
Call POST /gerar-token to gerar token de acesso
Automated Agendamento Management
Automate agendamento operations by combining multiple AgendamentoAPI endpoints. Agents can listar serviços disponíveis and then listar unidades diponíveis para o serviço in a single workflow.
Call GET /listarServicosAgendamento to listar serviços disponíveis, then verify the result
AI Agent Integration via Jentic
AI agents discover and call AgendamentoAPI 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 apiKey tokens manually.
Search Jentic for 'gerar token de acesso', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
14 endpoints — documentação da api para o agendamento do sistema attendance.
METHOD
PATH
DESCRIPTION
POST
/gerar-token
Gerar token de acesso
GET
/listarServicosAgendamento
Listar serviços disponíveis
GET
/listarUnidadesAgendamento
Listar unidades diponíveis para o serviço
POST
/salvarCliente
Insere ou atualiza um cliente
GET
/pesquisarCliente
Pesquisar cliente por número
GET
/pesquisarAgendamentosCliente
Pesquisar agendamento do cliente
GET
/pesquisarAgendamentosAgendado
Pesquisar agendamento agendados
GET
/listarGruposAgendamento
Listar dias e horários disponíveis para agendamento
POST
/gerar-token
Gerar token de acesso
GET
/listarServicosAgendamento
Listar serviços disponíveis
GET
/listarUnidadesAgendamento
Listar unidades diponíveis para o serviço
POST
/salvarCliente
Insere ou atualiza um cliente
GET
/pesquisarCliente
Pesquisar cliente por número
GET
/pesquisarAgendamentosCliente
Pesquisar agendamento do cliente
GET
/pesquisarAgendamentosAgendado
Pesquisar agendamento agendados
GET
/listarGruposAgendamento
Listar dias e horários disponíveis para agendamento
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AgendamentoAPI by hand means learning its x-auth-token header key, pointing at its us-east-1 gateway host, and handling retries yourself. Through Jentic you install once, import AgendamentoAPI from the API Directory, store the API key once, and your agent calls it.
Permission scoping
AgendamentoAPI carries scheduling targets in the request body and query, not in the URL path, so you limit the agent to the operations it needs, such as listing services or searching clients, and leave out client-saving unless you add it. Every operation the agent can call is one you chose to allow.
Credential isolation
Your AgendamentoAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list available scheduling services' or 'find a client's appointments', and Jentic returns the matching AgendamentoAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
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 AgendamentoAPI API through Jentic.
What authentication does the AgendamentoAPI use?
The AgendamentoAPI uses an API key passed in the `x-auth-token` header. 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 AgendamentoAPI?
Yes. Use the POST /gerar-token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the AgendamentoAPI?
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 AgendamentoAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the AgendamentoAPI have?
The AgendamentoAPI exposes 14 endpoints covering agendamento operations.
Can I limit what my agent is allowed to do with the Agendamento API?
Yes. Because you run Jentic One yourself, your own rules decide which Agendamento API operations and credentials the agent may use, so you can allow read-only calls like listing available services with GET /listarServicosAgendamento or searching a client with GET /pesquisarCliente while leaving out write operations. Client-saving through POST /salvarCliente stays off unless you explicitly add it, since Agendamento carries its scheduling targets in the request body and query rather than the URL path. Every operation the agent can call is one you chose to allow.
GET STARTED