CuraeAI Platform API

CuraeAI is Plaid for medical records: a hosted, HIPAA-grade connectivity platform. Your users link their health systems (EHRs) through a Curae-hosted Connect ceremony, and your backend reads normalized FHIR data over a server-to-server REST API.

The API is read + verification today (no data writes yet).

How an integration fits together

1. Connect — embed the Connect widget so a user links a health system. The widget calls a small backend proxy you host; your API key never reaches the browser.
2. Receive webhooks — the platform notifies your backend as connections authorize, data imports, and exports become ready.
3. Read records — fetch normalized FHIR resources (point reads) or queue an NDJSON export for a connection.

Core facts

• Base URL — https://api.curaeai.com (production), https://sandbox.curaeai.com (test mode), http://localhost:3000 (local dev). The REST surface lives under /api/platform/v1/* and /api/sdk/v1/*.
• Auth — server-to-server API keys, Authorization: Bearer <key>. Keys are cae_live_<…> (production) or cae_test_<…> (sandbox). They are secrets — never ship them to a browser.
• Versioning — send CuraeAI-Version: 2026-04-15. Dated versions; deprecations get a 12-month runway.
• Errors — RFC 7807 application/problem+json with a stable code.
• Pagination — cursor-based (opaque nextCursor).
• Idempotency — mutations accept an Idempotency-Key.

Start building

• Quickstart — your first integration.
• Authentication — keys and environments.
• Webhooks — receive and verify events.
• API reference — every endpoint, generated from OpenAPI.

Prefer to read code? The connect-quickstart starter runs the catalog → webhook loop end to end. AI agents: start at /llms.txt.