← Back to all docs
credible

Credible API

Credible is an electronic health record (EHR) platform used by behavioral health and human services organizations to manage clients, treatment plans, appointments, clinical notes, payer authorizations, and claims. With an unofficial API, you could synchronize client and staff rosters, create and doc

By Alex KlarfeldJanuary 25, 2026
Credible API

What is Credible?

Credible (from Qualifacts) is a comprehensive EHR designed for behavioral health and human services organizations, including community mental health centers, SUD treatment providers, IDD services, and residential programs. The platform spans clinical documentation, treatment planning, scheduling, client portal and telehealth, ePrescribing, labs/HIE connectivity, authorizations, and full revenue cycle management (837/835).

Core product areas include:

  • Client intake and demographics, program enrollments, and eligibility
  • Scheduling and attendance (individual and group)
  • Clinical documentation (progress notes, assessments, treatment plans)
  • Diagnoses, medications/ePrescribing, and care coordination
  • Payer authorizations and service codes specific to behavioral health (e.g., H2019, H0032, 90834)
  • Billing and claims (837P/I) with remittance reconciliation (835)
  • Reporting and outcomes measurement across programs

Common data entities:

  • Clients (patients) and caregivers/support contacts
  • Staff (clinicians, case managers, billers)
  • Programs, locations, and service lines
  • Appointments and group sessions (attendance, status)
  • Encounters/Services (documented care with billing details)
  • Authorizations (payer, units, service codes, date ranges)
  • Diagnoses and problem lists
  • Claims (837P/I) and remittances (835)

The Credible Integration Challenge

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

  • Program- and payer-specific rules: Behavioral health services vary by program (MH, SUD, IDD) and payer, affecting service codes, modifiers, units, and documentation requirements
  • Strong enterprise security: SSO/MFA and network controls complicate headless automation across staff roles and environments
  • Portal-first and reporting-heavy delivery: Key scheduling, documentation, and billing actions live in web apps and report exports, not unified public APIs
  • Batch interfaces and timing windows: SFTP/EDI feeds, batching constraints, and daily submission windows must be respected for claims and remits
  • Custom forms and data variability: Agency-specific forms and workflows create schema differences that need normalization for downstream automation

How Supergood Creates Credible APIs

Supergood reverse-engineers authenticated browser flows, report exports, and batch interfaces 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 claim objects so you can integrate once across programs/payers
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges report exports and SFTP/EDI flows with signed URL retrieval and delivery

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your API

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

  • Deploy with Monitoring

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

API 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.

Clients

GET/clients

Retrieve client demographics, program enrollments, diagnoses, and payer relationships. Use this to synchronize rosters and eligibility.

Authorizations

GET/authorizations

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

Encounters

POST/encounters

Create or update a documented service encounter with scheduling context, billing details, and verification metadata. Supports compliant edit reason codes and signatures.

Claims

POST/claims

Assemble an 837P/I claim from documented encounters. Supergood normalizes service lines and can route the generated file to the configured submission channel.

Use Cases

Roster and Scheduling Synchronization

- Push client and staff rosters from your CRM or HRIS into Credible - Create appointments automatically from your scheduling system with correct service codes and program/authorization references - Maintain a single source of truth for demographics, eligibility, and attendance

Authorization-Aware Service Delivery

- Validate authorizations before scheduling or encounter creation - Track remaining units and prevent over-utilization - Surface payer and program-specific rules to care coordinators

Clinical Documentation and Outcomes

- Pull treatment plans, diagnoses, and prior encounters to prefill documentation - Post progress notes and finalize encounters with audit trails and signatures - Aggregate outcomes across programs for analytics and quality improvement

Claims Generation and Reimbursement Automation

- Bundle documented encounters into 837P/I claims with payer-specific formatting - Submit via the configured channel (clearinghouse or payer portal) - Track claim statuses and reconcile remittances alongside encounter evidence

Audit and Compliance

- Export complete encounter packets with timestamps, providers, place of service, signatures, and reason codes - Maintain machine-readable audit trails aligned to behavioral health and payer requirements - Prove authorization checks and claim provenance during reviews

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 claim artifacts

Security

Encrypted transport, scoped tokens, and audit logging; respects Credible entitlements and compliance requirements

Webhooks

Optional asynchronous delivery for schedule updates, encounter finalizations, claim generation, and remittance updates

Latency

Sub-second responses for list/detail queries under normal load

Throughput

Designed for high-volume clinical 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

Frequently asked questions

Supergood supports workflows across commonly used Credible modules and agency-facing tools, subject to your licensing and entitlements. We scope coverage (e.g., clients, scheduling, authorizations, encounters, claim assembly) during integration assessment.

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For report/batch flows, we manage export timing windows, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically via SFTP/EDI.

Yes. You can assemble 837P/I from finalized encounters with payer-specific formatting. We can route submissions via your configured channel (clearinghouse or payer portal) and return statuses and artifacts for reconciliation.

We map custom forms and treatment plan fields into normalized objects, track attendance for group sessions, and preserve audit trails, signatures, and compliant reason codes during encounter edits.

Ready to get a real API?