Cedar

Supergood | Cedar API

Alex Klarfeld

Alex Klarfeld

— 6 min read
Supergood | Cedar API

Programmatically access patient billing, statements, balances, payments, and pre-visit estimates in Cedar with a stable REST API. Supergood builds and operates production-grade, unofficial Cedar integrations so your team can automate critical billing, patient financial engagement, and revenue cycle workflows without heavy custom engineering.

In plain English: Cedar is software that powers the patient financial experience for healthcare providers. It centralizes digital statements, payment plans, price estimates, insurance capture, and payment acceptance so patients can understand and resolve their bills. With an unofficial API, you could read real-time balances and statement details, initiate payments, create payment plans, update contact/insurance info, and pull pre-visit estimates to drive smarter scheduling and financial clearance.

If you’re a healthcare tech startup in billing or practice management, integrating with Cedar lets you pull and push concrete data and build features your providers will use. You can pull patient profiles, balances, statement line items, and estimate data; push payments and plan enrollments; and build eligibility-aware scheduling, outbound notifications, and consolidated payment experiences—all from your own product.

If a different tech company (for example, an RCM vendor or a patient engagement platform) wants to integrate with Cedar, you can synchronize rosters and contact data, surface accurate balances in-app, present up-to-date estimates and payment options, and post payments directly while keeping providers’ EHR/RCM systems reconciled.

  • Pull: Patient/guarantor profiles, statement summaries and itemized charges, balances, payment history, price estimates, insurance coverage/eligibility indicators
  • Push: Card/ACH/HSA payments, payment plan enrollments, contact detail updates, insurance policy updates, estimate acceptance, consent artifacts
  • Build: Consolidated billing dashboards across locations, estimate-aware scheduling and intake, propensity-to-pay segmentation, automated reminders and dunning, reconciliation with your EHR/RCM

What is Cedar?

Cedar is a patient financial engagement platform used by provider organizations and health systems to deliver clear digital billing, flexible payment options, price transparency, and pre-visit financial clearance. Cedar connects to EHRs and revenue cycle systems to generate patient-friendly statements, collect payments (card/ACH/HSA), offer payment plans and financial assistance workflows, and guide patients through pre-visit steps like insurance capture and estimate review.

Core product areas include:

  • Patient billing and payments (digital statements, payment acceptance, receipts)
  • Price estimates and pre-visit financial engagement (coverage capture, financial clearance)
  • Insurance management (primary/secondary policy updates, eligibility flags)
  • Payment plans and financial assistance workflows
  • Patient communications and self-service portals
  • Analytics and segmentation (propensity-to-pay, outreach optimization)

Common data entities:

  • Patients/Guarantors (demographics, contact preferences)
  • Statements/Invoices (balance due, due date, itemized charges)
  • Encounters/Visits (service dates, CPT/HCPCS codes, departments)
  • Payments (amounts, methods, receipts, applied statements)
  • Payment Methods (tokenized card, ACH, HSA)
  • Payment Plans (terms, installment schedules, status)
  • Price Estimates (services, expected patient responsibility, coverage)
  • Insurance Coverage (payer, member IDs, eligibility indicators)

The Cedar Integration Challenge

Providers rely on Cedar daily, but turning portal-based patient financial workflows into automated pipelines is hard:

  • Strong enterprise security: SSO/MFA, patient-link tokens, and network controls complicate headless automation
  • Portal-first delivery: Statements, payments, and estimate flows live in web apps with limited public APIs
  • Payment compliance: Tokenization, PCI considerations, and audit trails must be enforced for automated payments
  • EHR/RCM interfaces: Batch timing windows and reconciliation constraints require careful orchestration
  • Personalization: Segmented outreach and dynamic offers (e.g., payment plans) vary by patient and provider policy

How Supergood Creates Cedar APIs

Supergood reverse-engineers authenticated browser flows, batch interfaces, and network interactions to deliver a resilient API endpoint layer.

  • Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes patient, statement, payment, and estimate objects across health systems
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges batch exports and signed artifact retrieval where applicable (e.g., PDFs, receipts)

Use Cases

EHR-to-Billing Synchronization

  • Pull patient balances and statement details to power in-app billing
  • Maintain a single source of truth for demographics and coverage metadata
  • Surface accurate line items and charge descriptions from Cedar alongside EHR encounter context

Pre-Visit Estimates and Financial Clearance

  • Retrieve price estimates and coverage indicators before scheduling
  • Verify insurance and capture missing policy details
  • Present upfront costs and consent to improve collection rates

Payment Acceptance and Plan Enrollment

  • Post card/ACH/HSA payments directly against Cedar statements
  • Offer payment plans based on provider rules and patient eligibility
  • Generate receipts and keep EHR/RCM ledgers reconciled

Patient Engagement and Collections

  • Drive segmented outreach based on propensity-to-pay
  • Monitor payment statuses and follow up on past-due balances
  • Centralize communications and provide self-service billing portals

Audit and Compliance

  • Export statement PDFs, itemized charge lists, and payment receipts
  • Maintain machine-readable audit logs of payments and plan actions
  • Honor PCI and HIPAA requirements throughout billing workflows

Available Endpoints

Authentication

POST /sessions: Establish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/sessions \
  --header 'Authorization: Basic <Base64 encoded token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "username": "[email protected]",
    "password": "<password>",
    "mfa": {
      "type": "totp",
      "code": "123456"
    }
  }'

Example response

{
  "authToken": "eyJhbGciOi...",
  "expiresIn": 3600,
  "user": {
    "id": "u_4d9f21",
    "name": "Billing Admin",
    "entitlements": ["patients", "statements", "payments"]
  }
}

Patients

GET /patients: Retrieve patient/guarantor profiles with balances and coverage indicators. Use this to populate billing dashboards and route outreach.

Query parameters

  • mrn: string
  • lastName: string
  • activeBalanceOnly: boolean
  • updatedSince: ISO 8601 timestamp

Example response

{
  "items": [
    {
      "patientId": "pat_92b4c0",
      "mrn": "MRN-0012345",
      "name": {"first": "Avery", "last": "Nguyen"},
      "guarantorId": "gua_1a9f30",
      "contact": {
        "email": "[email protected]",
        "phone": "+1-312-555-0182",
        "preferred": "email"
      },
      "balances": {
        "totalBalance": 482.75,
        "activeStatements": 2,
        "lastStatementDate": "2026-01-15"
      },
      "insurance": {
        "primary": {"payerId": "payer_bcbs", "memberId": "ABCD12345", "eligible": true},
        "secondary": null
      },
      "propensityScore": 0.72,
      "paymentPlanActive": false,
      "updatedAt": "2026-01-20T18:12:04Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Statements

GET /statements: Retrieve current and historical statements with itemized charges, balances, and plan eligibility. Use this to present bills and compute payment distributions.

Query parameters

  • patientId: string
  • status: enum (open, paid, past_due)
  • issuedOn: ISO 8601 date
  • minBalance: number

Example response

{
  "items": [
    {
      "statementId": "stm_58d3e0",
      "statementNumber": "S-2026-000184",
      "patientId": "pat_92b4c0",
      "encounterId": "enc_7f93ab",
      "serviceDates": {"start": "2026-01-10", "end": "2026-01-10"},
      "balanceDue": 382.75,
      "dueDate": "2026-02-05",
      "status": "open",
      "charges": [
        {"code": "99213", "description": "Office/outpatient visit", "amount": 210.00},
        {"code": "80050", "description": "General health panel", "amount": 172.75}
      ],
      "provider": {"npi": "1234567890", "name": "Lakeview Medical Group"},
      "eligibleForPlan": true,
      "estimate": {
        "available": true,
        "estimatedPatientResponsibility": 382.75
      },
      "pdfUrl": "https://download.cedar.example/signed/abc123..."
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Payments

POST /payments: Post a payment against one or more Cedar statements. Supports tokenized card/ACH/HSA methods and returns receipt artifacts.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/payments \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "patientId": "pat_92b4c0",
    "statements": [
      {"statementId": "stm_58d3e0", "amount": 200.00},
      {"statementId": "stm_58d3e1", "amount": 182.75}
    ],
    "paymentMethod": {
      "type": "card",
      "token": "tok_visa_1f2c9e",
      "brand": "visa",
      "last4": "4242",
      "expMonth": 12,
      "expYear": 2028
    },
    "currency": "USD",
    "idempotencyKey": "pay-batch-jan20-0001",
    "referenceId": "portal-checkout-93301"
  }'

Example response

{
  "paymentId": "pay_71af2b",
  "status": "posted",
  "totalAmount": 382.75,
  "applied": [
    {"statementId": "stm_58d3e0", "amount": 200.00},
    {"statementId": "stm_58d3e1", "amount": 182.75}
  ],
  "receipt": {"url": "https://download.cedar.example/signed/receipt_71af2b.pdf", "createdAt": "2026-01-20T16:05:42Z"},
  "referenceId": "portal-checkout-93301"
}

Get full API Specs →

Technical Specifications

  • Authentication: Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
  • Response format: JSON with consistent resource schemas and pagination
  • Rate limits: Tuned for enterprise throughput while honoring licensing and usage controls
  • Session management: Automatic reauth and cookie/session rotation with health checks
  • Data freshness: Near real-time retrieval of statements, payments, and estimate artifacts
  • Security: Encrypted transport, scoped tokens, and audit logging; respects Cedar entitlements, HIPAA and PCI constraints
  • Webhooks: Optional asynchronous delivery for statement updates, payment postings, and plan status changes

Performance Characteristics

  • Latency: Sub-second responses for list/detail queries under normal load
  • Throughput: Designed for high-volume billing and payment posting pipelines
  • Reliability: Retry logic, backoff, and idempotency keys minimize duplicate actions
  • Adaptation: Continuous monitoring for UI/API changes with rapid adapter updates

Getting Started

  1. Schedule Integration Assessment

Book a 30-minute session to confirm your Cedar product mix, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened Cedar adapter tailored to your workflows and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Cedar evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Which Cedar products can this integration cover?

Supergood supports workflows across commonly used Cedar modules (e.g., Cedar Pay and Cedar Pre), subject to your licensing and entitlements. We scope coverage (statements, payments, estimates, plan enrollment) during integration assessment.

Q: How are MFA, SSO, and payment tokenization handled for automation?

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth where enabled. For payments, we use tokenized methods provided by Cedar and maintain PCI-conscious flows, returning receipts and applied distributions programmatically.

Q: Can I create payment plans or fetch pre-visit estimates via the API?

Yes. We can expose endpoints to create plan enrollments (terms, installment schedules) and retrieve estimates with coverage indicators and expected patient responsibility. Availability depends on your Cedar configuration and policies.

Waystar API - Programmatically access clearinghouse and RCM workflows with Supergood

Ready to automate your Cedar workflows?

Supergood can have your Cedar integration live in days with no ongoing engineering maintenance.

Get Started →

Read more