GET STARTED
TOOLS
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
Jentic publishes the only available OpenAPI specification for PawthosX.Business.API, keeping it validated and agent-ready. PawthosX is the business API behind ClinicOS, a veterinary practice management platform, and it exposes 590 endpoints covering appointments, cases, clients and patients, inventory, payments, prescriptions, lab panels, surgical records, scheduling, and clinic configuration. Authentication supports a Bearer token and an X-API-Key header, and the surface includes both interactive workflows (clocking in, kiosk, telnyx call control) and bulk export endpoints for clients and patients.
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.
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.
The Orthanc API exposes the full REST interface of the Orthanc DICOM server, letting clients ingest, retrieve, and orchestrate medical imaging data across studies, series, instances, and patients. It supports DICOM-Web (QIDO-RS, WADO-RS, STOW-RS), DICOMweb proxies, modality work-list queries, and asynchronous DICOM transfers, plus Lua and Python scripting hooks. With 299 endpoints, the API covers everything from raw instance retrieval to peer routing, anonymisation, and modification of imaging tags.
The Open Dental API exposes the practice management database used by thousands of dental clinics through a REST surface covering patients, appointments, treatments, claims, and accounting. With 215 endpoints across resources such as Patients, Appointments, Procedures, Claims, Allergies, and Recalls, it is the integration point for clinical add-ons, patient-engagement tools, billing reconcilers, and reporting dashboards that need bidirectional access to a clinic's chair-side data. Authentication uses an Authorization header carrying both the developer key and the practice-issued customer key.
Verifiable powers provider data, credentialing, and enrollment workflows for health plans, hospitals, and digital health companies. The Discovery API exposes 167 operations covering provider records, licenses, datasets, payer plans, credentialing requests, provider enrollments, monitoring alerts, audit logs, files, notes, webhooks, and integrations. Healthcare operations and provider-data teams use it to automate primary-source verification, monitor license status, and orchestrate credentialing pipelines.
Jentic publishes the only available OpenAPI specification for Hexfit API, keeping it validated and agent-ready. The Hexfit API gives fitness professionals and health practitioners programmatic access to clients, training plans, calendars, appointments, group sessions, and exercise libraries on the Hexfit platform. Across 162 endpoints it covers user management, training and meal plans, group memberships, in-session events, calendar booking, and metadata tagging, with regional hosts for Canada (ca) and Europe (eu). Authentication uses Bearer JWT for end-user calls and HTTP Basic for OAuth2 partner endpoints where the username is the client_id and password is the client_secret.
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.
Jentic publishes the only available OpenAPI specification for Mindbody Public API, keeping it validated and agent-ready. The Mindbody Public API v6 is the integration surface for fitness, wellness, and beauty studios using the Mindbody platform; its 142 endpoints cover appointments, classes, clients, enrollments, payroll, sales, site configuration, and staff. Authentication combines a developer API-Key header, a SiteId header that targets the studio, and a bearer staff user token issued via /usertoken/issue for actions that require a signed-in operator.
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.
Slicebox - safe sharing of medical images. The API exposes 118 endpoints.
Jentic publishes the only available OpenAPI specification for NCBI Datasets API, keeping it validated and agent-ready. The NCBI Datasets v2 API provides programmatic access to genome assemblies, gene records, taxonomy, BioSample metadata, prokaryote and virus sequence collections, and organelle datasets curated by the National Center for Biotechnology Information. Researchers, bioinformaticians, and AI agents use it to fetch data reports, sequence reports, and downloadable data packages by accession, taxon, BioProject, or BioSample identifier across 107 endpoints.
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.
Jentic publishes the only available OpenAPI specification for Health ID Service, keeping it validated and agent-ready. The NDHM Health ID Service issues and manages the ABHA Health ID - a unique identifier used across India's National Digital Health Mission to issue, access, and share health records with patient consent. The 73-endpoint surface covers Aadhaar and mobile-OTP based registration, KYC, profile management, password and credential recovery, health-facility linkage, integrated programs, search, and Health ID card generation in PDF, PNG, and SVG formats.
The Oura Ring API (V2) provides programmatic access to health and wellness data collected by the Oura Ring wearable device. The API exposes detailed biometric data including sleep tracking, readiness scores, activity metrics, heart rate variability (HRV), body temperature, stress levels, and daily movement. Oura users and partner applications can access this data through OAuth2 authentication with user consent. The API is designed for health apps, research studies, wellness platforms, and personal data integrations with a strong focus on webhook-based data delivery for real-time updates.
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.
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.
Jentic publishes the only available OpenAPI specification for Orion Health FHIR R4 API, keeping it validated and agent-ready. Orion Health is a global health-tech vendor whose FHIR R4 API exposes patient, clinical, encounter, and provider resources from its Health Information Exchange and EMR platforms. The 41 endpoints span Patient, Condition, Observation, AllergyIntolerance, Immunization, Procedure, DiagnosticReport, MedicationRequest, MedicationAdministration, MedicationDispense, Encounter, CarePlan, CareTeam, Appointment, ServiceRequest, Practitioner, Organization, and other FHIR resources, with OAuth 2.0 authorization. It is suitable for agent-driven clinical lookups, care-coordination tools, and SMART-on-FHIR style integrations.
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.
NextGen's FHIR R4 API provides standardized access to electronic health records through 21 clinical resource types including Patient, Observation, MedicationRequest, and DiagnosticReport. Built on the HL7 FHIR R4 standard, the API enables RESTful read and search operations across allergy records, care plans, immunizations, lab results, and encounter data. Healthcare applications can retrieve structured clinical data in JSON format with OAuth 2.0 security to support care coordination, population health analytics, and patient engagement workflows.
Jentic publishes the only available OpenAPI specification for the RCSB RESTful API, keeping it validated and agent-ready. The Research Collaboratory for Structural Bioinformatics (RCSB) Protein Data Bank exposes structured access to the canonical archive of three-dimensional macromolecular structures used in life sciences research and drug discovery. The 39-endpoint API covers entries, assemblies, polymer and non-polymer entities, entity instances, chemical components, interfaces, groups, schema, and repository holdings. Endpoints are public and require no authentication.
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.
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.
Jentic publishes the only available OpenAPI specification for Hexfit API, keeping it validated and agent-ready. Hexfit is a fitness and health management platform used by trainers, dietitians, and wellness professionals to manage clients, training programs, exercises, events, and documents. The API exposes 34 endpoints across user, business, training, document, event, and OAuth2 surfaces, including dedicated endpoints for client and professional onboarding and meta-data management. Both staging.api.myhexfit.com/v2 and api.myhexfit.com/v2 are served, authenticated with a bearer token.
The RxNorm API exposes the National Library of Medicine's normalized drug nomenclature, mapping brand names, generic names, NDCs, and clinical drug concepts to stable RxCUI identifiers. Agents can resolve drug name variants, traverse relationships between ingredients and clinical drug forms, retrieve historical NDC status, and check approximate term matches for misspellings. The dataset spans the full US prescription drug ecosystem with monthly updates from FDA and other source vocabularies. Suitable for medication reconciliation, e-prescribing validation, and clinical decision support pipelines.
The openEHR EHR REST API is the standardised specification published by the openEHR Foundation for interacting with electronic health records that follow the openEHR reference model. It defines 33 endpoints covering EHR creation, EHR_STATUS, COMPOSITION versioning, DIRECTORY folder structure, CONTRIBUTION audit objects, and ITEM_TAG annotations, each with versioned history. Vendor implementations such as Better, EhrBase, and Code24 expose this surface so that clinical applications written against the openEHR standard can run on any conformant backend without rewrite.
Jentic publishes the only available OpenAPI specification for Health Repository Provider Specifications for HIU, keeping it validated and agent-ready. This spec bundles the 32 endpoints that an entity acting as a Health Information User (HIU) must implement and consume to participate in India's NDHM network. It draws operations from the Gateway and Bridge specs and groups them under identification, consent flow, data flow, subscriptions, and monitoring - making it clear which calls an HIU originates against the Gateway and which callbacks the Gateway invokes against the HIU.
Jentic publishes the only available OpenAPI specification for Health Repository Provider Specifications for HIU, keeping it validated and agent-ready. This specification covers the endpoints a Health Information User must implement and call to participate in India's NDHM network - typically an insurer, doctor, telehealth platform, or research entity that needs consented access to patient records. The 32 endpoints cover identification, consent flow callbacks, health information requests and on-request callbacks, encrypted record receipt via /v0.5/health-information/transfer, and Gateway-facing helpers such as certs and OpenID configuration.
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.
The HHS Media Services API exposes the U.S. Department of Health & Human Services syndicated content library - public health campaigns, media items, languages, sources, and tags - for embedding in third-party sites and applications. Across 31 GET endpoints, integrators can search media items by keyword, list campaigns, retrieve campaign-specific media, fetch ready-to-embed snippets, and pull thumbnails or YouTube metadata. The API supports multi-column sorting via a sort query parameter (with a leading hyphen for descending order) and RFC 3339 dates, and is read-only with no authentication.
The Open Targets Platform REST API provides programmatic access to integrated genetic and clinical evidence linking targets to diseases for drug discovery research. Endpoints fall into public methods (stable, fully supported) for associations, evidence, and search; private methods used by the Open Targets web app for autocomplete, drug, disease, and target detail; and utils for service metrics and version info. Responses are JSON by default with optional xml, csv, and tab formats on some endpoints. The API is openly accessible and is the standard programmatic entry point for the Open Targets Platform's curated bioinformatics data.
The Open Targets Platform REST API serves the evidence linking genes and diseases for drug target discovery. An agent can search across targets, diseases, and drugs, retrieve the association between a target and a disease, read the underlying evidence, and pull platform statistics. It suits biomedical research and drug-discovery work that needs structured target-disease evidence rather than a manual literature review. The API is read-oriented and needs no credentials.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.