canonical: https://jentic.com/apis/clnto.com/clnto # Clnto API Jentic publishes the only available OpenAPI specification for Clnto API, keeping it validated and agent-ready. Clnto API is a healthcare and clinical data management interface that exposes patient records, appointment scheduling, and clinical record retrieval through a small set of REST endpoints. It is designed for clinical software teams that need to read and write patient demographics, manage appointment slots, and pull clinical records into downstream applications. The API uses bearer token authentication and operates on a versioned base URL at api.clnto.com/v1. ## For AI agents Read and write patient records, schedule appointments, and pull clinical history through a compact set of healthcare endpoints secured by bearer tokens. ## Scope Does not handle billing, claims processing, or pharmacy fulfilment - use for patient, appointment, and clinical record management only. ## Capabilities - Retrieve a patient profile by patient identifier - Register a new patient record with demographic and contact details - List upcoming appointments for a clinic or provider - Book a new appointment slot tied to a patient and provider - Pull clinical records linked to a specific patient - Update existing patient demographic and contact fields ## Use cases ### Patient Onboarding Register new patients into the clinical system with structured demographic and contact data so that downstream scheduling, billing, and clinical record systems can attach to a single patient identifier. The Clnto API exposes the patients endpoint for creation and the patients/{patientId} endpoint for lookup, allowing onboarding flows to confirm new identifiers immediately. Typical integrations cover a few hundred new patients per clinic per month and complete in under a day with bearer-token auth. Example prompt: Register a new patient with name, date of birth, and contact email, then read back the assigned patientId to confirm creation. ### Appointment Booking Schedule appointments for existing patients and list upcoming visits for a provider or clinic. The appointments endpoint supports both creating new bookings and listing existing ones, which lets reception and patient-portal flows surface availability and confirm slots in real time. Suitable for clinics handling a few hundred appointments per week without building a custom scheduling backend. Example prompt: List all appointments for the next seven days and book a 30-minute follow-up for patient ID 12345 with the assigned provider. ### Clinical Record Retrieval Pull clinical records associated with a patient for use in care continuity, second-opinion workflows, or analytics pipelines. The records endpoint returns structured clinical data tied to a patient identifier, so downstream agents can summarise history, populate intake forms, or feed reporting dashboards. Integration is straightforward given the small endpoint surface and bearer-token auth. Example prompt: Fetch all clinical records for patient ID 12345 and summarise the most recent diagnosis. ### AI Agent Clinical Assistant Allow AI agents to act on behalf of clinical staff by reading patient records, booking appointments, and updating demographics through Jentic. Agents discover Clnto operations by intent, load the relevant input schema, and execute the call without raw bearer tokens entering the model context. This pattern fits triage chatbots, voice-driven booking assistants, and admin copilots in small to mid-size clinics. Example prompt: Search Jentic for the Clnto patient lookup operation, load the schema, and retrieve the record for patient ID 12345 using a scoped Jentic credential. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /patients | List patients in the clinic system | | POST | /patients | Register a new patient record | | GET | /patients/{patientId} | Retrieve a single patient by ID | | GET | /appointments | List appointments for the clinic | | POST | /appointments | Book a new appointment | | GET | /records | Retrieve clinical records | ## Key resources - **Patients** — Create, read, and update patient demographic and contact records - **Appointments** — List and create appointment bookings tied to patients and providers - **Records** — Retrieve clinical records associated with a patient identifier ## Why Jentic - **Setup:** Wiring Clnto by hand means managing its bearer auth, mapping its patient, appointment, and clinical-record endpoints, and handling retries yourself against api.clnto.com/v1. Through Jentic you install once, import the Clnto API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Clnto puts the patient id in the URL path (/patients/{patientId}), so a rule can pin your agent to one patient: it can read that patient's record and nothing else. You choose the operations it may call, so creating patients or appointments are not included unless you add them. - **Credential handling:** Your Clnto bearer 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, which matters for HIPAA-aligned deployments. - **Discovery method:** Agents search Jentic by intent such as 'look up a patient record', and Jentic returns the matching Clnto operation with its input schema, so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **athenahealth API** — Larger ambulatory EHR platform with broader clinical coverage than Clnto - **Metriport API** — Aggregates medical records across networks to feed back into clinical systems - **Epic FHIR API** — Enterprise FHIR-based EHR API for large hospital networks ## FAQ ### Why is there no official OpenAPI spec for Clnto API? Clnto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clnto API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Clnto API use? The Clnto API uses HTTP bearer token authentication. Every request must include an Authorization header with a bearer token issued by Clnto. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and never enters the agent's context - agents receive scoped access at execution time only. ### Can I book appointments through the Clnto API? Yes. The /appointments endpoint accepts POST requests to create new bookings tied to a patient and provider, and GET requests to list existing appointments. Use it to drive booking flows, reschedule confirmations, and provider calendar views. ### What are the rate limits for the Clnto API? The OpenAPI spec does not declare explicit rate limits. Treat the API as a moderate-traffic clinical system: batch large reads, throttle automated workflows, and check Clnto's developer site at https://developers.clnto.com for the current published quota before going to production. ### How do I retrieve a patient record through Jentic? Search Jentic with the query 'look up a patient record', load the schema for the GET /patients/{patientId} operation, then execute with the patient identifier. Install the SDK with pip install jentic and call client.search, client.load, and client.execute in sequence. ### Does the Clnto API support clinical record retrieval? Yes. The /records endpoint returns clinical records linked to a patient identifier. It is the right entry point for care continuity flows, intake form pre-fill, and analytics pipelines that need patient history. ### Can I limit what my agent is allowed to do with the Clnto API? Yes. Because Jentic One is self-hosted, you write the rules that decide which Clnto operations your agent may call and which credential it uses. You can allow only read operations like GET /patients/{patientId} and GET /records while excluding POST /patients and POST /appointments, so the agent cannot register patients or book visits unless you add those operations. Since Clnto carries the patient id in the URL path, a rule can also pin the agent to a single patientId, letting it read that one patient's record and nothing else.