InstaMed

Supergood | InstaMed API

Alex Klarfeld

Alex Klarfeld

— 6 min read
Supergood | InstaMed API

Programmatically access patient billing, payment processing, remittance advice (ERA/835), and deposit reconciliation workflows in InstaMed with a stable REST API. Supergood builds and operates production-grade, unofficial InstaMed integrations so your team can automate collections, refunds, and reconciliation without heavy custom engineering.

In plain English: InstaMed is a healthcare payments platform used by providers, payers, and patients to send and pay bills, manage payment methods and plans, process card/ACH transactions, and reconcile insurance remittances and deposits. With an unofficial API, you could initiate and capture patient payments, synchronize statements and balances from your PM/EHR, fetch ERA files and deposit reports, apply refunds and adjustments, and surface reconciliation dashboards—end to end.

If you’re a healthcare tech startup building billing, practice management, or provider-facing tools, integrating your stack with InstaMed unlocks concrete data flows and features:

  • Pull: Patient statements and balances, transaction histories, settlement batches/deposits, remittance advice (ERA/835), payer and check details
  • Push: New payments (card/ACH), refunds, receipt delivery preferences, statement references/metadata for posting back to your PM/EHR
  • Build: Embedded checkout experiences, payment plan offers, automated payment posting, payer/provider reconciliation driven by ERA and deposit data, refund and adjustment workflows

What is InstaMed?

InstaMed (a J.P. Morgan company) provides a secure healthcare payment network used by providers, payers, and consumers to streamline patient billing and collections, process payments online and at point-of-care, manage payment methods and plans, and reconcile insurance remittances and deposits. InstaMed connects to PM/EHR systems, portals, and clearinghouse channels to consolidate payment acceptance and settlement reporting.

Core product areas include:

  • Patient billing and statements (online bill pay, eStatement delivery)
  • Payment acceptance (card-present and card-not-present; ACH/eCheck)
  • Stored payment methods and payment plans
  • Claims clearinghouse and ERA (835) remittance retrieval for reconciliation
  • Deposit reporting and settlement summaries
  • Refunds, adjustments, and chargeback management

Common data entities:

  • Patients/Guarantors
  • Statements/Invoices and balances
  • Transactions (card/ACH, authorization, capture, settlement)
  • Payment Methods (vaulted tokens, card, ACH)
  • Payment Plans (terms, installments, next due)
  • Remittances (ERA/835, payer, check, claim lines, adjustments)
  • Deposits/Settlement batches
  • Providers/Merchants and locations/terminals

The InstaMed Integration Challenge

Organizations rely on InstaMed daily, but turning portal-based payment and reconciliation workflows into automated pipelines is hard:

  • PCI + HIPAA requirements: Strict controls around card data, ACH credentials, and PHI complicate headless automation
  • Strong enterprise security: SSO/MFA and network policies introduce session management complexity
  • Portal-first delivery: Statements, transactions, and ERA artifacts often live in web apps or batch exports rather than unified public APIs
  • Settlement timing: Batching windows, file availability (ERA, deposit reports), and cutoffs must be respected
  • Posting logic: Mapping statements and transactions back to PM/EHR requires consistent identifiers and reconciliation rules

How Supergood Creates InstaMed 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 payment, statement, remittance, and deposit objects so you can integrate once across provider locations
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges batch exports and SFTP/EDI flows with signed URL retrieval and delivery for ERA/835 and deposit reports
  • Respects PCI principles: No storage of raw PAN/ACH data in your environment; tokenization and encryption via controlled flows

Use Cases

Patient Billing Automation

  • Pull statements and balances from InstaMed
  • Offer embedded checkout (card/ACH) and post payments back to your PM/EHR
  • Send receipts and update payment preferences

Point-of-Service Collections

  • Surface outstanding balances at check-in
  • Capture card-not-present payments with stored tokens or ACH authorizations
  • Keep front-desk workflows synchronized with settlement statuses

Payment Plan Management

  • Identify patients eligible for plans and display terms
  • Track installments, next due dates, and failed payments
  • Automate reminders and post-plan payments to ledgers

ERA and Deposit Reconciliation

  • Retrieve ERA (835) files for payer payments
  • Match remittance lines to claims and patient responsibility
  • Tie deposits and settlement batches to transaction-level records

Refund and Adjustment Workflows

  • Initiate partial or full refunds against transactions
  • Track reversal statuses and update patient balance/ledger
  • Monitor disputes and chargebacks alongside transaction history

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_3a19e7",
    "name": "Billing Admin",
    "entitlements": ["statements", "payments", "remittances"]
  }
}

Patient Statements

GET /statements: Retrieve patient statements with balances, due dates, and line items. Use this to power billing views and to validate payment posting.

Query parameters

  • patientId: string
  • statementNumber: string
  • status: string (open, closed, past_due)
  • dueBefore: ISO 8601 date
  • providerId: string

Example response

{
  "items": [
    {
      "statementId": "stm_71c90a",
      "statementNumber": "S-2025-11872",
      "patientId": "pat_9b42f0",
      "patientName": "Jordan Patel",
      "guarantorId": "gua_41cf92",
      "providerId": "prov_oh-1234",
      "balanceDue": 215.00,
      "currency": "USD",
      "dueDate": "2026-02-15",
      "status": "open",
      "invoiceNumbers": ["INV-100231", "INV-100232"],
      "lineItems": [
        {"description": "Office Visit", "serviceCode": "99213", "charge": 160.00, "insurancePaid": 0.00, "patientResponsibility": 160.00},
        {"description": "Lab Panel", "serviceCode": "80050", "charge": 120.00, "insurancePaid": 65.00, "patientResponsibility": 55.00}
      ],
      "createdAt": "2026-01-20T16:12:02Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Payments

POST /payments: Create a patient payment (card or ACH) against a statement/invoice. Supports immediate capture and receipt delivery.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/payments \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "patientId": "pat_9b42f0",
    "statementId": "stm_71c90a",
    "amount": 215.00,
    "currency": "USD",
    "method": {
      "type": "card",
      "card": {
        "number": "4111111111111111",
        "expiryMonth": 12,
        "expiryYear": 2027,
        "cvv": "123"
      }
    },
    "capture": true,
    "receipt": {"email": "[email protected]"},
    "referenceId": "pm-post-42391"
  }'

Example response

{
  "transactionId": "txn_58d3e0",
  "status": "captured",
  "authCode": "A12345",
  "network": "visa",
  "last4": "1111",
  "amount": 215.00,
  "currency": "USD",
  "statementId": "stm_71c90a",
  "createdAt": "2026-01-20T16:20:42Z",
  "referenceId": "pm-post-42391"
}

Remittances (ERA/835)

GET /remittances: Retrieve ERA remittance summaries and detail lines for payer payments. Use this for reconciliation and posting back to claims.

Query parameters

  • payerId: string
  • checkNumber: string
  • depositDateFrom: ISO 8601 date
  • depositDateTo: ISO 8601 date
  • claimId: string

Example response

{
  "items": [
    {
      "eraId": "era_71af2b",
      "payerId": "payer_bcbs-oh",
      "payerName": "BlueCross BlueShield Ohio",
      "checkNumber": "0051829",
      "depositDate": "2026-01-19",
      "totalPaid": 1280.50,
      "currency": "USD",
      "claimLines": [
        {
          "claimId": "clm_100231",
          "patientId": "pat_9b42f0",
          "serviceDate": "2026-01-05",
          "allowed": 160.00,
          "paid": 95.00,
          "patientResponsibility": 65.00,
          "adjustments": [
            {"code": "CO-45", "amount": 20.00, "reason": "Charge exceeds fee schedule"}
          ]
        }
      ],
      "downloadUrl": "https://download.instamed.example/signed/abc123..."
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

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, transactions, ERA, and deposit artifacts
  • Security: Encrypted transport, scoped tokens, and audit logging; respects InstaMed entitlements, PCI obligations, and HIPAA safeguards
  • Webhooks: Optional asynchronous delivery for payment captured/refunded, ERA availability, and deposit postings

Performance Characteristics

  • Latency: Sub-second responses for list/detail queries under normal load
  • Throughput: Designed for high-volume patient payments and reconciliation 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 InstaMed product mix, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

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

  1. Deploy with Monitoring

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

Schedule Integration Call →

Frequently Asked Questions

Q: Which InstaMed products can this integration cover?

Supergood supports workflows across commonly used InstaMed provider portals and payment reporting tools, subject to your licensing and entitlements. We scope coverage (e.g., statements and balances, payments, ERA/835 retrieval, deposit summaries) during integration assessment.

Q: How are MFA, PCI, and batch interfaces handled for automation?

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For batch flows, we manage SFTP/EDI timing windows, retrieve ERA/835 and deposit reports, and provide signed URLs or artifacts programmatically. We adhere to PCI principles—tokenizing card data and avoiding storage of raw PAN/ACH details.

Q: Can I reconcile payments and deposits alongside ERAs?

Yes. You can fetch ERA detail and deposit summaries, map remittance lines to claims and patient responsibility, and tie settlements to transaction-level records to achieve end-to-end reconciliation.

Ready to automate your InstaMed workflows?

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

Get Started →

Read more