Klingo App Klingo API Telefonia
Browse all Klingo App APIs62
AI ReadinessAI-Aware (B-)62/100
Community OpenAPI document · agent-readyHealthcareAppointment SchedulingapiKey8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Register incoming calls, list and confirm clinic appointments, capture NPS ratings, and read agenda blocks in Klingo's management system.
Use for: Register an incoming call for appointment confirmation, List appointments awaiting confirmation for today, Record a confirmation result for an appointment, Capture an NPS rating after an appointment
Not supported: Does not place outbound calls, process payments, or store medical records. Use for phone-based clinic appointment confirmation and NPS capture only.
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.
Install Jentic One Beta
Connect the Klingo API Telefonia to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Klingo API Telefonia, 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%2Fklingo.app%2Fklingo-telefonia" | 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%2Fklingo.app%2Fklingo-telefonia" | 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 Klingo API Telefonia API.
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
Patterns agents use Klingo API Telefonia API for, with concrete tasks.
★ 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.
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.
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.
Record an NPS rating and note for a given appointment id
Key Endpoints
8 endpoints — the klingo telefonia api handles phone-driven appointment confirmation for clinics using klingo's management system.
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
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
Jentic AI Readiness Score
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.
K
Klingo API Telefonia
- AI-Aware (B-)62/100
74
Foundational Compliance79
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability50
Security58
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
94%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
79
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
67%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
77%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
50%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
58
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
58%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Klingo API Telefonia API through Jentic.
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.
GET STARTED