WellSky

WellSky provides care coordination and home health software with REST APIs for managing patient referrals, authorizations, visit scheduling, clinical documentation, and billing workflows across home health, hospice, palliative care, personal care, and specialty pharmacy settings.

WellSky is listed with 4 APIs on the APIs.io network. Tagged areas include Healthcare, Home Care, Hospice, Care Coordination, and FHIR.

The WellSky catalog on APIs.io includes 1 JSON-LD context.

WellSky’s developer surface includes engineering blog, support, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

21.1/100 emerging ▬ flat Agent 3/100 human only Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

4 APIs

Healthcare Home Care Hospice Care Coordination FHIR Clinical Documentation Billing Electronic Health Records

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 21.1/100 · emerging

Contract Quality 2.3 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 4.0 / 17

Operational Transparency 0.8 / 11

Contract Governance 0.0 / 10

Discoverability 6.1 / 9

Regulatory Posture 1.8 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/wellsky/"><img src="https://apis.io/badge/wellsky/card.svg" alt="WellSky on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 10.7 — up to +22.3 composite points Ask about this →
Access Clarity scores 23.4 — up to +15.3 composite points Ask about this →
Developer Ergonomics scores 28.6 — up to +14.3 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/wellsky/apis.yml: open an issue on github.com/api-evangelist/wellsky to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
E-Prescribing (pharmacy, e-prescribing, medication data)	standard	60.0	-	-
IVD, Diagnostics and Surgical Devices (FDA / EU regulated device makers)	standard	60.0	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

WellSky CareTend API

Integration hub API for WellSky's CareTend home infusion and specialty pharmacy platform, providing programmatic access to patient management, billing authorizations, clinical v...

WellSky FHIR API

FHIR R4-compliant API built on the US Core Implementation Guide, providing read access to patient health data including demographics, conditions, medications, lab results, care ...

WellSky Hospice and Palliative API

FHIR R4 interoperability API for EHR partners integrating with WellSky's Consolo hospice and palliative care platform, supporting patient demographics, care plans, medication re...

WellSky Personal Care Connect API

FHIR-compliant API for WellSky Personal Care software platform enabling data integration and interoperability for home care agencies, built on OAuth 2.0 client credentials flow ...

WellSky API pricing

Not yet checked against WellSky's own pricing page. Compiled by API Evangelist on 2026-06-13; confirm before you rely on a figure.

Plan	Price
CareTend API Access	—
WellSky FHIR API Access	—
Hospice and Palliative API Access	—
Personal Care Connect API Access	—

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

WellSky Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

WellSky Rate Limits

4 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

WellSky

11 quoted statements, read from WellSky's own page on 2026-11-10.

TERMS

Eligibility 1

Who may sign up and where, quoted from its own terms.

WellSky

2 quoted statements, read from WellSky's own page on 2026-11-10.

ELIGIBILITY

Data License 1

How its data and outputs may be reused, quoted from its own terms.

WellSky

1 quoted statement, read from WellSky's own page on 2026-11-10.

LICENSE

FinOps 1

Cost, billing, and metering signals for API financial operations.

WellSky Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Wellsky Context

39 classes · 5 properties

JSON-LD

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

WellSky Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Plans

FinOps

UsageTerms

DataLicense

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Eligibility

Eligibility

Source (apis.yml)

aid: wellsky
name: WellSky
description: WellSky provides care coordination and home health software with REST APIs for managing patient referrals, authorizations,
  visit scheduling, clinical documentation, and billing workflows across home health, hospice, palliative care, personal care,
  and specialty pharmacy settings.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/wellsky.png
url: https://raw.githubusercontent.com/api-evangelist/wellsky/refs/heads/main/apis.yml
created: '2026-06-13'
modified: '2026-10-06'
specificationVersion: '0.23'
type: Index
tags:
- Healthcare
- Home Care
- Hospice
- Care Coordination
- FHIR
- Clinical Documentation
- Billing
- Electronic Health Records
tags_raw:
- Healthcare
- Home Health
- Hospice
- Care Coordination
- FHIR
- Clinical Documentation
- Billing
- EHR
- Home Care
apis:
- aid: wellsky:caretend-api
  name: WellSky CareTend API
  description: Integration hub API for WellSky's CareTend home infusion and specialty pharmacy platform, providing programmatic
    access to patient management, billing authorizations, clinical visits, inventory, purchase orders, and document workflows.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://caretendapi.readme.io/
  baseURL: https://api.wellsky.com
  tags:
  - Home Infusion
  - Specialty Pharmacy
  - Patient Management
  - Billing
  - Inventory
  properties:
  - type: Documentation
    url: https://caretendapi.readme.io/
  - type: Authentication
    url: https://caretendapi.readme.io/docs/getting-started
  contact:
  - FN: WellSky Support
    url: https://wellsky.com/support/
- aid: wellsky:fhir-api
  name: WellSky FHIR API
  description: FHIR R4-compliant API built on the US Core Implementation Guide, providing read access to patient health data
    including demographics, conditions, medications, lab results, care plans, and clinical documents for ConnectEHR interoperability.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wellsky.dynamicfhir.com/wellsky/basepractice/r4/Home/ApiDocumentation
  baseURL: https://wellsky.dynamicfhir.com/fhir/wellsky/basepractice/r4
  tags:
  - FHIR
  - Electronic Health Records
  - Interoperability
  - USCDI
  - Clinical Data
  tags_raw:
  - FHIR
  - EHR
  - Interoperability
  - USCDI
  - Clinical Data
  properties:
  - type: Documentation
    url: https://wellsky.dynamicfhir.com/wellsky/basepractice/r4/Home/ApiDocumentation
  contact:
  - FN: WellSky Support
    url: https://wellsky.com/support/
- aid: wellsky:hospice-palliative-api
  name: WellSky Hospice and Palliative API
  description: FHIR R4 interoperability API for EHR partners integrating with WellSky's Consolo hospice and palliative care
    platform, supporting patient demographics, care plans, medication requests, observations, encounters, and CEHRT data-blocking
    compliance requirements.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://mediwareinc.github.io/consolo.interop-api-docs/
  baseURL: https://mediwareinc.github.io/consolo.interop-api-docs/
  tags:
  - Hospice
  - Palliative Care
  - FHIR
  - EHR Integration
  - CEHRT
  properties:
  - type: Documentation
    url: https://mediwareinc.github.io/consolo.interop-api-docs/
  contact:
  - FN: WellSky Consolo Support
    email: consolo.support@wellsky.com
- aid: wellsky:personal-care-connect-api
  name: WellSky Personal Care Connect API
  description: FHIR-compliant API for WellSky Personal Care software platform enabling data integration and interoperability
    for home care agencies, built on OAuth 2.0 client credentials flow for scheduling, care worker management, and visit data.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://apidocs.clearcareonline.com/
  baseURL: https://apidocs.clearcareonline.com/
  tags:
  - Personal Care
  - Home Care
  - Scheduling
  - FHIR
  properties:
  - type: Documentation
    url: https://apidocs.clearcareonline.com/
  - type: TermsOfService
    url: https://wellsky.com/clearcare-connect-api-terms/
  contact:
  - FN: WellSky Support
    url: https://wellsky.com/support/
common:
- url: https://wellsky.com/feed/
  type: BlogRSS
- type: Website
  url: https://www.wellsky.com/
- type: DomainSecurity
  url: security/wellsky-domain-security.yml
- type: Blog
  url: https://wellsky.com/blog/
- type: Support
  url: https://wellsky.com/support/
- type: Plans
  url: plans/wellsky-plans-pricing.yml
- type: RateLimits
  url: rate-limits/wellsky-rate-limits.yml
- type: FinOps
  url: finops/wellsky-finops.yml
- type: UsageTerms
  url: terms/wellsky-terms-of-service.yml
- type: Eligibility
  url: eligibility/wellsky-eligibility.yml
- type: DataLicense
  url: data-license/wellsky-data-license.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

WellSky API — frequently asked questions

Does WellSky have an API?

Yes. APIs.io lists 4 APIs from WellSky, including WellSky CareTend API, WellSky FHIR API and WellSky Hospice and Palliative API, and 1 more.

How do I authenticate with the WellSky API?

WellSky uses bearer-token authentication.

How much does the WellSky API cost?

APIs.io lists 4 pricing plans for WellSky, with each plan's price, limits and inclusions under Pricing on this page.

Is the WellSky API ready for AI agents?

WellSky has a Kin Score of 21.1 out of 100 (emerging) and an Agent Readiness score of 3.1 (human-only), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/wellsky"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/wellsky/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/wellsky/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.