canonical: https://jentic.com/apis/swaggerhub.qsi-swagger/api-do-app-client-do-attendance

# Qsi Swagger API do App client do Attendance

Documentação da API para o App do cliente do sistema Attendance. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically recuperar um atendimento do sistema attendance, reativa um atendimento no sistema attendance. Covers 5 operations with bearer authentication.

## Scope

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

## Capabilities

- Recuperar um atendimento do sistema Attendance
- Reativa um atendimento no sistema Attendance
- Confirma o atendimento pelo whatsapp
- Query and filter API do App client do Attendance records by parameters
- Monitor API do App client do Attendance operational status and events

## Use cases

### Developer Tools Operations

Use the API do App client do Attendance to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including recuperar um atendimento do sistema attendance, reativa um atendimento no sistema attendance, recuperar o número do whatsapp da unidade.

Example prompt: Call GET /recuperar-atendimento to recuperar um atendimento do sistema attendance

### Automated AppClientAttendanceAPI Management

Automate appclientattendanceapi operations by combining multiple API do App client do Attendance endpoints. Agents can reativa um atendimento no sistema attendance and then recuperar o número do whatsapp da unidade in a single workflow.

Example prompt: Call POST /reativar-atendimento to reativa um atendimento no sistema attendance, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API do App client do Attendance 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 bearer tokens manually.

Example prompt: Search Jentic for 'recuperar um atendimento do sistema attendance', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /recuperar-atendimento | Recuperar um atendimento do sistema Attendance |
| POST | /reativar-atendimento | Reativa um atendimento no sistema Attendance |
| GET | /get-numero-whatsapp | Recuperar o número do whatsapp da unidade |
| POST | /confirmar-atendimento-whatsapp | Confirma o atendimento pelo whatsapp |
| GET | /recuperar-link-pesquisa | Recuperar o link da pesquisa da unidade |

## Key resources

- **AppClientAttendanceAPI** — Serviços disponíveis para o App do cliente do sistema Attendance

## Why Jentic

- **Setup:** Wiring the API do App client do Attendance by hand means managing its JWT bearer token, pointing at its us-east-1 gateway host, and coding retries yourself. Through Jentic you install once, import the API do App client do Attendance from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** This API carries its targets in the request body and query, not in the URL path, so you limit the agent to the operations it needs, such as recovering an attendance or fetching the WhatsApp number, and leave out reactivation unless you add it. Every operation the agent can call is one you chose to allow.
- **Credential handling:** Your token for the API do App client do Attendance 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.
- **Discovery method:** Agents search Jentic by intent such as 'recover an attendance' or 'get the WhatsApp contact number', and Jentic returns the matching API do App client do Attendance 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 do App client do Attendance use?

The API do App client do Attendance uses a Bearer token in the Authorization 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 recuperar um atendimento do sistema attendance with the API do App client do Attendance?

Yes. Use the GET /recuperar-atendimento endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API do App client do Attendance?

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 recuperar um atendimento do sistema attendance through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'recuperar um atendimento do sistema attendance'. Jentic returns the matching API do App client do Attendance operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API do App client do Attendance have?

The API do App client do Attendance exposes 5 endpoints covering appclientattendanceapi operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which App Client Attendance operations and credentials the agent may use, so you can allow only read calls like recovering an attendance (GET /recuperar-atendimento) or fetching a unit's WhatsApp number (GET /get-numero-whatsapp) while leaving out state-changing calls such as reactivating an attendance (POST /reativar-atendimento). Since this API carries its targets in the request body and query rather than the URL path, scoping happens at the operation level, and every operation the agent can call is one you chose to allow. Your bearer token stays with your self-hosted instance and is injected only for the calls you permit.