Credible

Supergood | Credible API

Alex Klarfeld

Alex Klarfeld

— 6 min read
Supergood | Credible API

Programmatically access client records, payer authorizations, clinical encounters, and reimbursement workflows in Credible with a stable REST API. Supergood builds and operates production-grade, unofficial Credible integrations so your team can automate intake-to-billing pipelines without heavy custom engineering.

In plain English: Credible is an electronic health record (EHR) platform used by behavioral health providers to manage clients, appointments, treatment plans, documentation, authorizations, and billing to Medicaid and commercial payers. With an unofficial API, you could read and write client demographics, insurance coverage, authorization limits, progress notes/encounters, and charge details—then orchestrate claims and remittance reconciliation end to end.

From the perspective of a healthcare tech startup focused on billing or practice management: integrating with Credible means you can pull clients, payers, authorizations, and encounter data into your system; push schedules, notes, and charges back to Credible; and build features like authorization-aware scheduling, pre-billing validation, automated claim assembly, denial analytics, and reconciliation dashboards. A different tech company—say, a care coordination app or a provider group’s BI tool—could use the same integration to keep rosters current, monitor utilization against authorizations, and surface operational metrics driven by encounter and reimbursement data.

If you’re a clinic, provider group, or revenue cycle team, integrating your tech stack with Credible unlocks concrete data flows and features:

  • Pull: Client profiles, insurance coverage, payer authorizations, treatment plans, scheduled appointments, encounter/progress notes, charge status, claim statuses, remittance summaries
  • Push: New/updated clients from your CRM/intake, appointments/schedules, documented encounters with CPT/HCPCS codes and units, compliant edits, charge submissions referencing authorizations
  • Build: Authorization-aware scheduling, pre-billing rules and eligibility checks, automatic charge assembly from documentation, reconciliation dashboards combining encounter, claim, and 835 remittance data

What is Credible?

Credible (by Qualifacts) is a behavioral health EHR used by community mental health centers, provider groups, and human services agencies. It supports intake and referrals, client demographics, treatment planning, clinical documentation, scheduling, authorization tracking, ePrescribing, outcomes, and comprehensive revenue cycle management spanning charge creation through claims submission and remittance reconciliation.

Core product areas include:

  • Client intake and demographic management
  • Scheduling and appointment management
  • Clinical documentation (progress notes, encounters, treatment plans)
  • Payer authorizations and service programs
  • Charge capture and coding (CPT/HCPCS, modifiers, units, diagnosis)
  • Claims generation and submission to Medicaid/MCOs and commercial payers
  • Remittance (835) processing and reconciliation
  • Reporting, audit trails, and compliance support

Common data entities:

  • Clients (patients)
  • Staff/Providers
  • Appointments/Schedules
  • Encounters/Progress Notes (time in/out, procedure codes, diagnoses, documentation)
  • Authorizations (payer/program, service code, units, validity dates)
  • Payers/Insurance policies
  • Charges and claim line items (837P/I)
  • Remittances (835) and adjustments/denials

The Credible Integration Challenge

Organizations rely on Credible daily, but turning portal-based clinical and billing workflows into automated pipelines is hard:

  • Program- and payer-specific rules: Medicaid/MCOs and commercial payers use distinct service definitions, modifiers, units, and authorization logic
  • Enterprise security: SSO/MFA and strict entitlements complicate headless automation and service account usage
  • Portal-first delivery: Key documentation, authorization checks, and billing actions often live in web apps or batch exports rather than unified public APIs
  • File interfaces and submission timing: SFTP/EDI feeds, batching constraints, and daily submission windows must be respected to avoid rejections
  • Compliance nuances: Encounter edits require compliant reason codes and audit trails; documentation and retention rules vary by jurisdiction and program

How Supergood Creates Credible 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 client, authorization, encounter, and billing objects so you can integrate once across programs and payers
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges batch exports and SFTP/EDI flows with signed URL retrieval and delivery where applicable

Use Cases

EHR-to-RCM Synchronization

  • Push client rosters from your intake or CRM into Credible
  • Create appointments automatically from your scheduling system
  • Keep demographics, insurance, and eligibility aligned across systems

Authorization-Aware Scheduling and Utilization

  • Validate payer authorizations before appointment creation or encounter documentation
  • Track remaining units and prevent over-utilization
  • Surface program-specific rules to schedulers and care teams

Documentation-to-Charge Automation

  • Map progress notes to CPT/HCPCS codes, units, and diagnosis codes
  • Apply compliant edit reason codes with audit trails for late entries or corrections
  • Route incomplete notes back for correction before charge creation

Claims and Reimbursement Automation

  • Bundle validated encounters into 837P/I claims with payer-specific formatting
  • Submit via configured channels (state portals, MCO gateways, clearinghouses)
  • Track claim statuses and reconcile remittances alongside encounter evidence

Audit and Compliance

  • Export complete encounter packets with timestamps, codes, signatures, and reason codes
  • Maintain machine-readable audit trails aligned to program requirements
  • Prove documentation integrity and claim provenance during reviews

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_c29a71",
    "name": "Billing Admin",
    "entitlements": ["clients", "authorizations", "encounters", "billing"]
  }
}

Clients

GET /clients: Retrieve client demographics, insurance coverage, and identifiers. Use filters to scope by payer, date updated, or active status.

Query parameters

  • mrn: string
  • status: string (active, discharged)
  • updatedSince: ISO 8601 timestamp
  • payerId: string
  • page: integer
  • pageSize: integer

Example response

{
  "items": [
    {
      "clientId": "cli_91b4f0",
      "mrn": "MRN-002184",
      "firstName": "Jordan",
      "lastName": "Patel",
      "dateOfBirth": "1988-05-11",
      "sex": "M",
      "phone": "+1-614-555-0199",
      "email": "[email protected]",
      "address": {
        "line1": "100 Community Ave",
        "city": "Columbus",
        "region": "OH",
        "postalCode": "43215"
      },
      "status": "active",
      "primaryDiagnosis": "F41.1",
      "insurance": [
        {
          "payerId": "payer_oh-medicaid",
          "planName": "Ohio Medicaid",
          "memberId": "OHM-778201",
          "eligibilityStatus": "active",
          "effectiveStart": "2026-01-01",
          "effectiveEnd": null
        }
      ],
      "updatedAt": "2026-01-19T15:00:02Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Authorizations

GET /authorizations: Retrieve payer/member service authorizations with allowed units, service codes, and date ranges. Use this to validate scheduling, documentation, and claim eligibility.

Query parameters

  • clientId: string
  • payerId: string
  • serviceCode: string (CPT/HCPCS)
  • activeOn: ISO 8601 date
  • program: string

Example response

{
  "items": [
    {
      "authorizationId": "auth_7342c1",
      "authorizationNumber": "A-2026-11872",
      "clientId": "cli_91b4f0",
      "clientName": "Jordan Patel",
      "payerId": "payer_oh-medicaid",
      "program": "Outpatient Behavioral Health",
      "serviceCode": "90834",
      "modifiers": ["U1"],
      "unitsAuthorized": 24,
      "unitsRemaining": 18,
      "startDate": "2026-01-01",
      "endDate": "2026-03-31",
      "status": "active"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Encounters

POST /encounters: Create or update a clinical encounter/progress note with time in/out, coding, diagnoses, and authorization references. Supports compliant edit reason codes and audit fields.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/encounters \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clientId": "cli_91b4f0",
    "providerId": "prv_41cf92",
    "authorizationId": "auth_7342c1",
    "payerId": "payer_oh-medicaid",
    "serviceCode": "90834",
    "modifiers": ["U1"],
    "diagnosisCodes": ["F41.1"],
    "timeIn": "2026-01-19T14:02:33Z",
    "timeOut": "2026-01-19T14:52:33Z",
    "units": 1,
    "placeOfService": "11",
    "notes": "60-minute psychotherapy session focused on anxiety management.",
    "editReasonCodes": [],
    "referenceId": "ehr-schedule-42391"
  }'

Example response

{
  "encounterId": "enc_58d3e0",
  "chargeStatus": "ready",
  "documentationStatus": "signed",
  "exceptions": [],
  "createdAt": "2026-01-19T15:02:02Z",
  "referenceId": "ehr-schedule-42391"
}

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 clients, authorizations, encounters, and billing artifacts
  • Security: Encrypted transport, scoped tokens, and audit logging; respects Credible entitlements and compliance requirements
  • Webhooks: Optional asynchronous delivery for encounter creation, charge readiness, and remittance updates

Performance Characteristics

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

  1. Supergood Builds and Validates Your API

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

  1. Deploy with Monitoring

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

Schedule Integration Call →

Frequently Asked Questions

Q: Which Credible modules can this integration cover?

Supergood supports workflows across commonly used Credible modules subject to your licensing and entitlements. We scope coverage (e.g., client rosters, authorizations, encounters/notes, charge readiness, claim status, remittance retrieval) during integration assessment.

Q: How are MFA, SSO, 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, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically.

Q: Can I validate authorizations during scheduling and documentation?

Yes. You can check units remaining and service eligibility in real time before creating appointments or finalizing encounters, helping prevent denials and over-utilization.

Sandata API - Programmatically access EVV and Medicaid workflows with Supergood

Ready to automate your Credible workflows?

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

Get Started →

Read more