Skip to main content
Discharge API · Sandbox

Build hospital-to-home into your workflow.

Search the verified clinical workforce, submit one-click discharge referrals, and resolve geography — programmatically. Get a self-serve sandbox key in seconds.

Try it live

Your sandbox key

Paste an existing sandbox key, or request one — it's issued instantly to your inbox.

Endpoints

Base URL https://caraloom.com/api

GET/v1/healthpublic

Liveness probe. No authentication required.

GET/v1/clinicians/search key required

Search the verified clinical workforce by state, city, ZIP, or diagnosis. Returns de-identified sandbox data.

Query: state, city, zip, diagnosis, limit

POST/v1/discharge-referrals key required

Submit a discharge referral and instantly receive matched, verified clinicians.

Body: { "primary_diagnosis": "CHF", "care_type": "Skilled Nursing", "zip": "78701" }

GET/v1/geo/zip/{zip} key required

Resolve a ZIP to its nearest service city + state.

POST/v1/webhooks key required

Register the endpoint that receives signed event callbacks. Returns a signing secret once.

Body: { "url": "https://your-app.com/hooks", "events": ["referral.created"] }

Example

curl "https://caraloom.com/api/v1/clinicians/search?state=TX&limit=3" \
  -H "Authorization: Bearer clk_sandbox_YOUR_KEY"

FHIR R4 — Hospital-to-Home

R4

For Epic, Cerner, and integration engines: every endpoint below returns a real FHIR R4 resource (proper resourceType, US-Core profile reference, Bundle searchset on search, and OperationOutcome on errors). The CapabilityStatement is public; reads/writes use the same sandbox API key as the native endpoints above.

GET/v1/fhir/metadatapublic

FHIR R4 CapabilityStatement — read this to discover supported resources and search params.

GET/v1/fhir/Patient/{id} key required

Read a Patient resource (US-Core profile reference).

Example: /v1/fhir/Patient/abc-123

GET/v1/fhir/Encounter/{id} key required

Read an Encounter resource (HL7 v3 class=HH, home health visit).

GET/v1/fhir/Encounter key required

Search Encounters. Returns a Bundle (searchset).

Example: ?patient=abc-123&status=in-progress&_count=10

GET/v1/fhir/ServiceRequest/{id} key required

Read a ServiceRequest representing a discharge referral.

GET/v1/fhir/ServiceRequest key required

Search ServiceRequests. Returns a Bundle (searchset).

Example: ?patient=abc-123&status=active&_count=10

POST/v1/fhir/ServiceRequest key required

Create a discharge referral via a real FHIR R4 ServiceRequest resource. Fires the referral.created webhook.

Fetch the CapabilityStatement

curl "https://caraloom.com/api/v1/fhir/metadata" \
  -H "Accept: application/fhir+json"

Create a discharge referral (FHIR ServiceRequest)

curl -X POST "https://caraloom.com/api/v1/fhir/ServiceRequest" \
  -H "Authorization: Bearer clk_sandbox_YOUR_KEY" \
  -H "Content-Type: application/fhir+json" \
  -d '{
    "resourceType": "ServiceRequest",
    "status": "active",
    "intent": "order",
    "subject": { "display": "Jane Doe, MRN-12345" },
    "priority": "urgent",
    "reasonCode": [{
      "coding": [{
        "system": "http://hl7.org/fhir/sid/icd-10-cm",
        "code": "I50.9",
        "display": "Heart failure"
      }]
    }],
    "note": [{ "text": "Needs IV diuretic monitoring at home." }]
  }'

Try it live

Runs against the live sandbox using the key above.

Webhooks

Register an endpoint to receive signed event callbacks (referral.created, referral.matched, ping). Every delivery is signed with HMAC-SHA256 over the raw body in the X-CaraLoom-Signature: sha256=… header — verify it with your signing secret.

Your webhook URL

Verify a signature (Python)

import hmac, hashlib
sig = hmac.new(SECRET.encode(), raw_body, hashlib.sha256).hexdigest()
assert request.headers["X-CaraLoom-Signature"] == f"sha256={sig}"

Sandbox vs. production

Sandbox

  • • De-identified demo data
  • • 60 req/min · 5,000 req/day
  • • Referrals stored in a sandbox store
  • • Self-serve key, instant

Production

  • • Real write-through to the live discharge pipeline
  • • Per-org configurable rate limits
  • referral.created / referral.matched webhooks
  • • Activated by our team —

Every response includes a rate object with your remaining quota. A 429 with Retry-After is returned when a window is exhausted.

OpenAPI & Swagger

A machine-readable OpenAPI 3.0 spec — import it into Postman, generate a client, or explore it interactively below.

CaraLoom Discharge API
 v1 
OAS 3.0

https://caraloom.com/api/v1/openapi.json

Search the verified clinical workforce, submit one-click discharge referrals, and resolve geography. Sandbox keys return de-identified demo data; production keys write real referrals into the live pipeline and emit signed webhooks. Authenticate with Authorization: Bearer <key> or X-API-Key.

Servers

Clinicians

Referrals

Geo

Webhooks

System

CaraLoom

Care, woven into one continuous thread. From discharge to accepted placement to first visit — one record, one promise.

care@caraloom.com

Chantilly, VA 20151 · Serving providers nationwide

HIPAA-ready End-to-end encrypted Background-checked

CaraLoom is a technology marketplace, not a direct care provider. Clinicians are independent licensed professionals. We verify identity and licenses at onboarding and monitor them on an ongoing basis; because no screening is exhaustive, use your judgment when choosing care. See our Trust & Safety page.

A marketplace, not a care provider

CaraLoom is a technology marketplace and care-coordination platform — not a healthcare provider, staffing agency, or employer of clinicians. Clinicians are independent, licensed professionals who run their own practices. Bookings, rates, and care plans are agreements made directly between families and clinicians.

Payments & settlement

CaraLoom is a software platform and not a bank, escrow agent, or money transmitter. We utilize third-party payment processors (Stripe and Stripe Connect) to facilitate direct clinician-to-family transactions based on verified service-delivery milestones. Funds are secured up-front at booking and scheduled for payout once the clinician signs the clinical visit log.

Profiles & verification

Profiles, reviews, and messages are created by our users. We verify each clinician's identity and license at onboarding and monitor license status on an ongoing basis. No screening is ever exhaustive, so we encourage families to interview clinicians and use their own judgment when choosing care. See what we check on our Trust & Safety page.

AI guidance

Cara and other AI features are informational and are not a substitute for professional medical advice, diagnosis, or treatment. Please talk to your physician or another qualified provider about any medical question.

Emergencies

If you are experiencing a medical emergency, call 911.

Promotions & marks

Promotional offers and referral rewards are subject to their stated terms and may change. CaraLoom℠ and “Care that comes home to you.” are service marks of CaraLoom, Inc. © 2026 CaraLoom, Inc. Your use of this site is subject to our Terms of Service and Privacy Policy.

© 2026 CaraLoom, Inc. All rights reserved. Care, woven into one continuous thread.

Get started

Install CaraLoom

Add to your home screen for one-tap access.