Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API DirectoryBrowse 10,000+ APIs ready for AI agent integration API ScorecardAssess your APIs for AI-readiness with automated scoring Agentic SandboxSafely simulate AI agents with your production APIs Jentic MiniFree, self-hosted API execution layer for AI agents

CAPABILITIES

IntegrationConnect AI agents to your existing systems WorkflowsDiscover and capture successful agent workflows GovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentation Arazzo EditorBuild and edit multi-step API workflows visually

Developers

GET STARTED

DocumentationGuides and API reference QuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples

Resources

BlogLatest articles and insights Press & MediaBrand assets and press contact Open StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.

Company

About UsOur mission and team CareersJoin our team ContactGet in touch

Sign in Book a Demo

How Jentic Works API Directory API Scorecard Agentic Sandbox Jentic Mini Integration Workflows Governance Arazzo UI Arazzo Editor

Documentation Quickstart GitHub

Blog Press & Media Open Standards Newsletter

About Us Careers Contact

Request a demo Sign Up

Sign up for exclusive Jentic updates

Website

For Developers

Docs
GitHub

Company

About
Blog
Careers
Contact us

© 2026 Jentic. All rights reserved.

Terms & Conditions•Privacy Policy•

Healthcare APIs | Jentic

APIs/Healthcare

Healthcare APIs

Explore APIs in this category. Connect any of them to your AI agent through Jentic.

Browse Healthcare APIs

Filters

Developer Tools

Communications

Data Enrichment

E Commerce

Productivity

CRM

Payments

Marketing

Media

Finance

Identity Auth

AI/ML

Cloud Infrastructure

Analytics

Security

HR recruiting

Maps Geolocation

Storage

IOT

Healthcare

Education

Social Media

Government

Fintech

Transportation

Business Operations

Collaboration

Gaming

Data Intelligence

Business Tools

Communication

Data

Artificial Intelligence

Backend As A Service

Media Content

Health Fitness

Content Management

Advertising

Project Management

Sales

Email Marketing

Events

Mapping

Reference Data

Business Intelligence

Hospitality

Legal Government

Incident Management

Supply Chain

Business Data

Business

Logistics

Workforce Management

Data Extraction

Human Resources

Design Collaboration

Marketing Advertising

Lifestyle

Payments Fintech

Unknown

Blockchain

Monitoring

Automation

Devops

Geospatial

Database

Hr

Networking

Commerce

A-Z

Most Popular

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.

1upHealth API Collection - All endpoints

Aggregate patient health data from multiple EHRs, health systems, and payers through a unified FHIR-based interface with 21 endpoints. The API supports user management, OAuth 2.0 token exchange, FHIR R4 and DSTU2 resource access, bulk data export, provider search, health system connectivity, and granular permission management. Connect to hundreds of health systems and retrieve Patient, Observation, MedicationRequest, DocumentReference, and other FHIR resources through a single integration point.

Adastra IVR API

Introduction The API provides option to search for a patient based on the phone number and the date of birth and create a case if the details match. The API exposes 3 endpoints secured with bearer authentication.

AIRe Link API

Jentic publishes the only available OpenAPI specification for AIRe Link API, keeping it validated and agent-ready. AIRe Link is a remote-care and clinical-collaboration platform that lets healthcare providers run video calls, collect structured clinical guides, manage clients and contacts, and exchange files with patients and partner clinicians. The API surfaces 324 operations across accounts, calls, clients, contacts, devices, exports, file libraries, forms, guide templates, and webhooks, making it suitable for embedding remote-consultation flows into a wider EHR or care-coordination product. Authentication is via the X-API-Key header.

Amazon HealthLake

Jentic publishes the only available OpenAPI specification for Amazon HealthLake, keeping it validated and agent-ready. Amazon HealthLake is a HIPAA-eligible service that stores, transforms, queries, and analyses FHIR-formatted health data in the cloud. The control-plane API manages FHIR datastores and the import and export jobs that move bulk FHIR resources in and out of those datastores. With 13 operations it is a focused control surface for provisioning HealthLake infrastructure and running data movement jobs.

Athena Health

Access and manage electronic health records including patient demographics, appointments, clinical charts, lab results, and provider information across athenahealth-connected practices. The API supports 38 endpoints covering patient registration, appointment scheduling, medication tracking, vital signs retrieval, and clinical document exchange via CCDA format. OAuth 2.0 client credentials flow ensures secure practice-level access with scoped tokens per practice ID.

Availity API

Jentic publishes the only available OpenAPI specification for Availity API, keeping it validated and agent-ready. The Availity API exposes US healthcare payer connectivity for revenue-cycle workflows, including payer list lookups, eligibility and benefits checks, and prior-authorization service reviews. Authentication uses OAuth 2.0 client-credentials, and responses follow X12 270/271 and 278 transaction semantics through a JSON facade. The current spec covers four operations across token issuance, payer discovery, and service-review lifecycle.

Care Plan 2.0

External Clinical API **Internal IDs** The following terms are used to reference IDs that identify resources in AlayaCare: - id - created_by - client_id - employee_id - plan_id - diagnosis_id - goal_id - intervention_id **External IDs** The following terms are used to reference IDs that identify resources systems external to AlayaCare: - external_employee_id - external_client_id - external_service. The API exposes 38 endpoints secured with basic authentication.

cBioPortal web Public API [Alpha]

Jentic publishes the only available OpenAPI specification for cBioPortal web Public API, keeping it validated and agent-ready. cBioPortal is the cancer genomics portal that hosts curated mutation, copy number, structural variant, and clinical data across hundreds of public studies. The API exposes endpoints for browsing studies, fetching sample and patient cohorts, retrieving mutation and copy number alterations, and pulling clinical attributes for downstream analysis. Most data fetch operations use POST bodies that take lists of study, sample, or gene identifiers, with matched GET endpoints for browsing.

Claim.MD API

Jentic publishes the only available OpenAPI specification for Claim.MD API, keeping it validated and agent-ready. Claim.MD is a healthcare claims clearinghouse used by US providers and billers to submit electronic claims, run eligibility checks, retrieve electronic remittance advice (ERA), and manage appeals and provider enrollments. The API exposes the full claim lifecycle through a single /services/* surface, including X12 270/271 eligibility, 835 remittance retrieval, and PDF or structured ERA data. Authentication is via an AccountKey query parameter taken from the Claim.MD web portal.

ClinicalTrials.gov API

Search, filter, and retrieve clinical study records from the ClinicalTrials.gov database — the world's largest registry of clinical trials with over 500,000 studies across 220 countries. The v2 API provides 6 endpoints for full-text study search with field-level filtering, individual study retrieval by NCT ID, metadata inspection, and statistical queries. No authentication is required for public access.

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.

Cloud Healthcare API

The Cloud Healthcare API stores and serves clinical data on Google Cloud using the standards healthcare systems already speak: FHIR R4/STU3/DSTU2 for structured records, HL7v2 for messaging, and DICOM for imaging. Datasets and stores act as logical containers, and operations cover read, write, search, bulk export, de-identification, consent management, and conformance to FHIR ImplementationGuides. The API also includes a consent service for tracking patient authorisations and an analytics export path that streams resources to BigQuery for population queries. It is the managed substrate behind many production EHR integrations, AI medical-imaging pipelines, and HIPAA-aligned research workloads on Google Cloud.

CMS Provider Data API

Jentic publishes the only available OpenAPI specification for CMS Provider Data API, keeping it validated and agent-ready. The API exposes the public Centers for Medicare and Medicaid Services provider datasets — hospitals, nursing homes, dialysis facilities, home health agencies, hospices, and physicians — through DKAN-style query, download, and SQL endpoints. Callers can search the dataset catalog, fetch metadata schemas, and run filtered queries against any individual distribution to retrieve quality measures, ratings, and provider directory data without authentication.

Co-WIN Certificate API

Jentic publishes the only available OpenAPI specification for Co-WIN Certificate API, keeping it validated and agent-ready. The Co-WIN Certificate API exposes the Indian government's Co-WIN portal endpoint for downloading official COVID-19 vaccination certificates as PDF files. The endpoint accepts a beneficiary reference and returns the certificate document signed by the Ministry of Health and Family Welfare. Authentication uses an API key in the Authorization header alongside an OAuth 2.0 authorization code flow against the DIVOC realm.

CommCare HQ API

Jentic publishes the only available OpenAPI specification for CommCare HQ API, keeping it validated and agent-ready. CommCare HQ is Dimagi's mobile data collection and case management platform used widely in global health, social services, and frontline worker programs. The API exposes 17 endpoints to read and write cases, ingest XForm submissions, list mobile and web users, fetch applications and lookup tables (fixtures), and pull SMS message history. Operations are scoped to a CommCare project space (the {domain} path parameter) and most are read-oriented, with case create/update via XML and form submission via the legacy receiver endpoint.

Core Server API

Jentic publishes the only available OpenAPI specification for Nabla Core Server API, keeping it validated and agent-ready. Nabla is an AI clinical assistant that turns ambient clinical conversations into structured notes, normalized clinical data, and patient instructions. The Core Server API is the server-side variant for backend integrations: it issues OAuth tokens, manages clinician users, and runs the core ambient operations such as listening to encounters, generating digests and notes, normalizing clinical data, and producing patient-facing instructions.

Core User API

Jentic publishes the only available OpenAPI specification for Nabla Core User API, keeping it validated and agent-ready. Nabla is an AI clinical assistant that produces structured notes, normalized clinical data, and patient instructions from ambient encounter audio. The Core User API is the client-side variant: it powers clinician-facing applications with operations for transcription, digest generation, normalization, patient instructions, dot phrases, custom dictionary expressions, and JWT refresh and logout. It uses an HTTP bearer token minted per clinician.

CoV-Spectrum LAPIS API

The CoV-Spectrum LAPIS API is the open data backend behind cov-spectrum.org, exposing 40 endpoints for querying SARS-CoV-2 sequence and metadata aggregates. Endpoints cover aligned and unaligned nucleotide sequences, aligned amino acid sequences per gene, nucleotide and amino acid mutations and insertions, phylogenetic subtrees, most-recent common ancestor lookups, sample details and aggregations, and a generic /query/parse helper. The base URL is the open v2 LAPIS endpoint and no authentication is required, making it suitable for public health dashboards, research pipelines, and academic agents that need bulk SARS-CoV-2 surveillance data.

Coviu Telehealth Video API

Jentic publishes the only available OpenAPI specification for Coviu Telehealth Video API, keeping it validated and agent-ready. The Coviu API powers the Coviu telehealth video platform, used by clinicians and allied health practices for secure video consultations. It exposes operations for creating and managing video sessions, adding and removing participants, monitoring waiting room queues, and retrieving collections data including submission files and audio recordings. Authentication is via OAuth 2.0 client credentials, HTTP Basic, or bearer token, depending on the integration model.

CROssBAR Data API

The CROssBAR Data API from EMBL-EBI exposes integrated biomedical reference data drawn from ChEMBL, DrugBank, UniProt, IntAct, EFO, HPO, and PubChem behind a single REST surface. Researchers can query molecules, assays, activities, drugs, proteins, EFO disease terms, HPO phenotypes, IntAct molecular interactions, and PubChem bioassays, compounds, and substances. The API powers exploratory pipelines that need cross-database biomedical context without separate integrations for each underlying source.

Dentally API

Jentic publishes the only available OpenAPI specification for Dentally API, keeping it validated and agent-ready. Dentally is cloud-based dental practice management software used by independent practices and groups, primarily across the UK and APAC. The API exposes 31 endpoints covering patients, appointments, fees, invoices, NHS claims, contracts, custom fields, payment plans, accounts, and acquisition sources. Sandbox and APAC base URLs are provided alongside production, enabling integrations that span dental groups, recall systems, and patient-engagement tools.

DentiMax Communicator API

Jentic publishes the only available OpenAPI specification for DentiMax Communicator API, keeping it validated and agent-ready. DentiMax Communicator is the patient-communication layer attached to the DentiMax dental practice management suite, used by US dental practices for scheduling and outbound patient messaging. The API exposes three endpoints covering listing appointments, scheduling appointments, and sending messages directly to a patient. Authentication uses a header API key, and the surface is intentionally narrow to support reminder, confirmation, and booking flows.

DrChrono

Access a full-featured EHR and practice management platform covering clinical documentation, patient records, appointment scheduling, billing, lab orders, prescriptions, and insurance eligibility across 310 endpoints. The API supports OAuth 2.0 authorization code flow with granular scopes for billing, patient data, clinical notes, and scheduling. DrChrono connects clinical workflows from charting to claims submission within a single integration.

Epic on FHIR API

Jentic publishes the only available OpenAPI specification for Epic on FHIR API, keeping it validated and agent-ready. Retrieve patient demographics, clinical observations, and medication requests from Epic-connected health systems using FHIR R4 resources. The API provides read access to Patient, Observation, and MedicationRequest resources, enabling interoperable health data retrieval from one of the largest EHR networks in the United States serving over 305 million patient records.

Everfit API

The Everfit API gives personal trainers and coaching businesses programmatic access to the Everfit fitness coaching platform. Thirteen operations cover authentication, inviting and archiving clients, looking up clients by ID or email, listing programs, and assigning clients to programs and autoflows. Authentication is via API key (originally exposed for Zapier-style automations), and the API is well suited to syncing client lifecycle events between Everfit and a CRM, an email marketing tool, or an internal coach assistant.

Eyefinity EHR FHIR API

Jentic publishes the only available OpenAPI specification for Eyefinity EHR FHIR API, keeping it validated and agent-ready. The API exposes a slice of the Encompass EHR through the FHIR R4 standard, focusing on patient demographics, clinical conditions, and the FHIR capability statement endpoint. It is intended for integrators building patient-record reads against Encompass-powered optometry practices and complies with the ONC information-blocking interoperability requirements.

Eyefinity Optometry EHR FHIR API

Jentic publishes the only available OpenAPI specification for Eyefinity Optometry EHR FHIR API, keeping it validated and agent-ready. The API exposes the Eyefinity Optometry electronic health record over the FHIR R4 standard, covering Patient, Condition, Procedure, Observation, MedicationRequest, AllergyIntolerance, Immunization, CarePlan and additional resources commonly needed for clinical reads. It is targeted at integrators building patient-record viewers, care-coordination tools, and analytics on Eyefinity-powered optometry practices.

Fitbit Web API Explorer

The Fitbit Web API exposes consented user health and activity data captured by Fitbit wearables, the Aria scale, and manual logs. The 122 endpoints cover activity, heart rate, sleep, body composition, breathing rate, ECG, cardio fitness (VO2 Max), temperature, irregular rhythm notifications, foods, friends, devices, and intraday time-series data at minute or second resolution. Authorization is OAuth 2.0 with per-scope user consent, suitable for digital health apps, employer wellness programmes, and research studies.

Fitness API

The Google Fitness API gives apps programmatic access to a user's fitness tracking data, including steps, heart rate, distance, calories, and workout sessions. It exposes data sources, raw datasets, aggregated reads, and named sessions, all scoped to the authenticated user. Apps can read existing data from connected wearables and write new data points or sessions captured by their own clients.

FuzeRx Pharmacy & Telehealth API

The FuzeRx API provides access to pharmacy and telehealth infrastructure including patient management, prescription handling, fill requests, transfers, insurance, copay requests, coverage requests, and prior authorizations. The API exposes 28 endpoints secured with apiKey authentication.

Gateway

Jentic publishes the only available OpenAPI specification for Gateway, keeping it validated and agent-ready. The NDHM Gateway is the central hub of India's National Digital Health Mission that routes interactions between Consent Managers (CMs), Health Information Providers (HIPs), and Health Information Users (HIUs). The 48-endpoint surface covers care-context discovery, account linking, consent flows, health-data flow, identification, and monitoring — split across CM-facing, HIP-facing, and HIU-facing roles. Authorisation uses signed JWTs distributed via the Gateway's openid-configuration and certs endpoints.

Gateway

Jentic publishes the only available OpenAPI specification for Gateway, keeping it validated and agent-ready. The NDHM Gateway is the central routing hub of India's National Digital Health Mission, brokering interactions between Consent Managers, Health Information Providers, and Health Information Users. It exposes 48 endpoints grouped into discovery, link, consent flow, data flow, monitoring, and session management, plus the well-known OpenID configuration and JWT signing certificate endpoints. Participants register with the Gateway and call its APIs to find each other, raise consent, and exchange encrypted health records under the NDHM 0.5 specification.