canonical: https://jentic.com/apis/klingo.app/klingo-telefonia

# Klingo App Klingo API Telefonia

The Klingo Telefonia API handles phone-driven appointment confirmation for clinics using Klingo's management system. It registers an incoming call for appointment handling, lists appointments awaiting confirmation on a given date, records confirmation results with their status and notes, captures NPS satisfaction ratings, and reports schedule blocks on a doctor's agenda. Access is controlled by an application token in a request header.

## For AI agents

Register incoming calls, list and confirm clinic appointments, capture NPS ratings, and read agenda blocks in Klingo's management system.

## Scope

Does not place outbound calls, process payments, or store medical records. Use for phone-based clinic appointment confirmation and NPS capture only.

## Capabilities

- Register an incoming phone call for appointment handling with the caller's CPF and extension
- List appointments awaiting confirmation for a given date
- Record an appointment confirmation result with its status and notes
- Capture an NPS satisfaction rating for an appointment
- List schedule blocks on a doctor's agenda
- Retrieve a single appointment by its id

## Use cases

### Confirm appointments by phone with an AI agent

An AI agent integration created through Jentic drives a phone confirmation flow. The Klingo Telefonia API registers the incoming call, lists the appointments due for confirmation that day, and records the confirmation result with its status, so the agent can run the call and write the outcome back into Klingo.

Example prompt: Register an incoming call, list appointments for the date, and record a confirmation result with its status

### Daily confirmation worklist

Clinic staff need the list of appointments to confirm each morning. The Klingo Telefonia API returns the appointments awaiting confirmation for a specific date, so an automation can build the day's call worklist and track which have been confirmed.

Example prompt: List appointments for today's date and return those still awaiting confirmation

### Capture satisfaction after a visit

Clinics measure patient satisfaction after attendance. The Klingo Telefonia API records an NPS rating with its note against an appointment, letting an agent capture the score at the end of a follow-up call and store it alongside the booking.

Example prompt: Record an NPS rating and note for a given appointment id

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/entrada` | Register an incoming call for appointment handling |
| GET | `/lista/{data}` | List appointments for confirmation on a date |
| POST | `/confirmar` | Record an appointment confirmation result |
| POST | `/nps` | Update the NPS rating for an appointment |
| GET | `/bloqueios` | List schedule blocks on a doctor's agenda |
| GET | `/{id}` | Retrieve a selected appointment |

## Key resources

- **Call entry** — Register an incoming call for appointment handling with caller and extension details
- **Appointments** — List appointments for confirmation by date and retrieve one by id
- **Confirmations** — Record confirmation results with status and notes
- **NPS** — Capture satisfaction ratings against an appointment
- **Agenda blocks** — List schedule blocks on a doctor's agenda

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 79 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/klingo.app/klingo-telefonia/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Klingo Telefonia by hand means setting the X-APP-TOKEN header on every call and matching the right base path for the telephony service. Through Jentic you install once, import Klingo Telefonia from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The appointment and confirmation details travel in the request body, so rules bound which operations your agent may call, not which appointment. You can allow the listing and confirmation operations while leaving NPS updates and agenda-block reads out unless you add them.
- **Credential handling:** Your Klingo application token 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 'confirm an appointment' or 'list appointments for a date', and Jentic returns the matching Klingo Telefonia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Calendly** — Calendly schedules meetings from availability links; Klingo Telefonia confirms clinic appointments by phone.
- **Acuity Scheduling** — Acuity manages appointment booking and intake; Klingo Telefonia is scoped to phone confirmation inside Klingo.
- **Sinch** — Sinch sends SMS and voice messages; pair it with Klingo Telefonia to send reminders around the confirmations it records.

## FAQ

### What authentication does the Klingo Telefonia API use?

The Klingo Telefonia API authenticates with an application key sent in the X-APP-TOKEN request header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

### Can I confirm an appointment with the Klingo Telefonia API?

Yes. The confirmation endpoint records a result against an appointment with its status and notes, and the listing endpoint returns the appointments due for confirmation on a date, so an agent can run a phone confirmation flow end to end.

### Can I capture an NPS rating after a visit?

Yes. The NPS endpoint updates a satisfaction rating with its note against an appointment id, so an agent can record the score at the end of a follow-up call and store it alongside the booking.

### How do I confirm appointments through Jentic?

Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Klingo Telefonia API from the API Directory and search for 'confirm a clinic appointment by phone'. Store the application token once and your agent can list and confirm appointments. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Klingo Telefonia MCP server?

You don't need an MCP server to give your agent the Klingo Telefonia API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls it, with each operation discovered on demand instead of loaded into the agent's context.

### Can I limit what my agent is allowed to do with the Klingo Telefonia API?

Yes. Write a rule that allows only the appointment-listing and confirmation operations, so the agent can read the day's worklist and record confirmations while NPS updates and agenda blocks stay out of reach. Every action it takes is recorded in an audit log.