← Back to all docs
aba billing services

ABA Billing Services API

If you’re another healthcare tech company—say an EHR, scheduling platform, or RCM analytics tool—integrating with ABA Billing Services means you can pull patient insurance details, authorizations, session validation results, claim statuses and remittances; push patient/provider rosters, billable ses

By Alex KlarfeldJanuary 25, 2026
ABA Billing Services API

What is ABA Billing Services?

ABA Billing Services provides billing and revenue cycle management solutions tailored to ABA therapy practices. Their services and tools span benefit verification, authorization management, documentation review, claims submission (commercial and Medicaid), posting of remittances, and denial follow-up, alongside education and coding resources specific to ABA (e.g., 97151, 97153, 97155, 97158 and Medicaid H-codes).

Core product areas include:

  • Authorization and benefit verification
  • Patient/client and provider rosters (BCBAs, RBTs)
  • Session documentation review and validation against payer rules
  • Claims generation and submission (837P/I) with payer-specific formatting
  • ERA/EOB posting, reconciliation, and denial management
  • Credentialing status tracking and payer enrollment support

Common data entities:

  • Patients/Clients (demographics, coverage, eligibility)
  • Providers (BCBA, RBT, supervising provider relationships, NPIs)
  • Authorizations (payer, service code, units, date ranges)
  • Sessions/Encounters (date/time, CPT/H-codes, modifiers, minutes/units, POS, diagnosis codes)
  • Claims (service lines built from validated sessions)
  • Remittances (ERA/EOB summaries, payments, adjustments, denial codes)
  • Payers and plans
  • Credentialing records (enrollment steps, effective dates)

The ABA Billing Services Integration Challenge

Organizations rely on ABA Billing Services to keep cash flowing, but turning portal-driven RCM workflows into automated pipelines is hard:

  • Payer-specific rules: Each commercial plan and Medicaid program enforces distinct codes, modifiers, POS, time rounding, and supervision requirements
  • Strong enterprise security: SSO/MFA and strict account controls complicate headless automation
  • Portal-first delivery: Authorization tracking, documentation review, and ERA posting often live in web apps or batch exports, not public APIs
  • EDI and timing windows: Clearinghouse submissions, SFTP feeds, and batching constraints must be respected
  • Compliance nuances: Session edits require compliant reason codes and audit trails; retention policies and PHI controls vary by payer
  • COB and multi-payer flows: Primary/secondary submissions and resubmissions add complexity to orchestration

How Supergood Creates ABA Billing Services 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 authorizations, sessions, claims, and ERA objects so you can integrate once across payers
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges clearinghouse and SFTP/EDI flows with signed URL retrieval and file delivery where applicable

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your API

We deliver a hardened ABA Billing Services adapter tailored to your workflows and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as ABA Billing Services 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.

Authorizations

GET/authorizations

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

Service Sessions

POST/service-sessions

Create or update a billable ABA session record with CPT/H-codes, time, POS, and supervising provider metadata. Supports compliant edit reason codes and validation.

Claims

POST/claims

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

Use Cases

EHR-to-Billing Synchronization

- Push patient and provider rosters from your EHR (e.g., CentralReach, WebABA, Rethink) into ABA Billing Services - Create billable session records automatically from your scheduling system with correct CPT/H-codes, modifiers, place of service, and supervising BCBA - Maintain a single source of truth for demographics, coverage, and eligibility

Authorization-Aware Scheduling and Utilization

- Validate authorizations before session creation and time entry - Track remaining units by code and prevent over-utilization - Surface payer-specific rules to care coordinators and schedulers

Session Validation and Documentation

- Pull validation results (e.g., minutes rounding, required supervision, modifier checks) and route issues to staff - Apply compliant reason codes on session edits with audit trails - Lock documentation prior to claim generation for clean submissions

Claims Generation and Reimbursement Automation

- Bundle validated sessions into 837P/I claims with payer-specific formatting and diagnosis pointers - Submit via the configured channel (payer portal or clearinghouse) and receive status updates - Post ERAs/EOBs, reconcile payments and adjustments, and route denials to worklists

Audit and Compliance

- Export session packets with timestamps, codes, modifiers, POS, supervising provider, and reason codes - Maintain machine-readable audit trails aligned to payer requirements - Prove claim provenance from authorization to remittance 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 authorizations, sessions, claims, and remittance artifacts

Security

Encrypted transport, scoped tokens, and audit logging; respects ABA Billing Services entitlements and compliance requirements

Webhooks

Optional asynchronous delivery for validation results, claim generation, and remittance updates

Latency

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

Throughput

Designed for high-volume session ingestion 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 ABA Billing Services portals and agency-facing tools, subject to your licensing and entitlements. We scope coverage (e.g., authorizations, documentation validation, claim assembly, ERA/EOB posting) during integration assessment.

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

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

Ready to get a real API?