← Back to all docs
webaba

WebABA API

WebABA is practice management and EHR software used by ABA therapy organizations to schedule sessions, document care, track authorizations, and bill insurance. An unofficial API would let you sync clients and staff from your systems, create and update sessions with correct CPT code

By Alex KlarfeldJanuary 25, 2026
WebABA API

What is WebABA?

WebABA provides EHR and practice management software for Applied Behavior Analysis (ABA) therapy practices. It supports client intake, scheduling and appointments, session documentation and progress notes, payer authorization tracking, and insurance billing (including generation of 837P claims and reconciliation with 835 remittances). Organizations use WebABA to manage RBTs and BCBAs, capture supervision and treatment plan details, and coordinate payer policies and compliance.

Core product areas include:

  • Scheduling and appointment management
  • Client records, guardians, payers, and policies
  • ABA session documentation (CPT codes such as 97151, 97153, 97155, 97156, 97158) and progress notes
  • Payer authorizations (units, date ranges, service codes, place of service)
  • Timesheets, supervision tracking (BCBA/RBT)
  • Claims generation and submission; remittance reconciliation
  • Telehealth flags and client portal workflows

Common data entities:

  • Clients (demographics, guardians, diagnoses, payers)
  • Staff (BCBAs, RBTs, schedulers, billing role)
  • Appointments/Sessions (start/end, CPT code, units, POS, telehealth, supervision)
  • Authorizations (service code, units authorized/remaining, validity dates, payer)
  • Treatment plans and progress notes
  • Payers and policies
  • Claims (837P service lines referencing documented sessions)
  • Remittances (835 summaries for reconciliation)

The WebABA Integration Challenge

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

  • Authorization nuances: Units are often in 15-minute increments per CPT code with date range limits; keeping them in sync manually is error-prone
  • Supervision requirements: BCBA supervision minutes and rendering provider roles must be captured accurately for compliance and billing
  • Limited public APIs: Key scheduling, note completion, and claim status workflows live in web apps and batch exports rather than unified APIs
  • Clearinghouse dependencies: EDI submission windows, payer-specific formatting, and ERA retrieval workflows add timing and delivery constraints
  • Security practices: MFA/SSO and role entitlements complicate headless automation for large agencies
  • Reporting exports: CSV-centric reporting makes programmatic, near real-time data access challenging

How Supergood Creates WebABA 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, session, and claim objects so you can integrate once across payer policies
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges batch exports and SFTP/EDI flows where applicable with signed URL retrieval and delivery

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your API

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

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as WebABA 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 ABA client profiles with demographics, guardians, payer policies, and diagnosis codes. Use this to synchronize rosters and drive scheduling.

Authorizations

GET/authorizations

Retrieve payer authorizations by client and CPT code with allowed units, date ranges, and place of service. Use this to validate scheduling and billable session creation.

Sessions

POST/sessions

Create or update an ABA therapy session record with start/end times, CPT service details, telehealth and POS metadata, supervision, and documentation status. Supports compliant edits and note references.

Claims

POST/claims

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

Use Cases

EHR-to-Practice Synchronization

- Push clients and staff rosters from your HRIS/EHR into WebABA - Create appointments automatically from your scheduling system with correct CPT codes, modifiers, and place of service - Maintain a single source of truth for demographics, guardians, and payer policies

Authorization-Aware Scheduling and Eligibility

- Validate authorizations before scheduling or session creation - Track remaining units and prevent over-utilization by CPT code and modifier - Surface payer rules (POS, telehealth flags, supervision requirements) to coordinators

Session Documentation and Supervision Tracking

- Pull draft and completed notes to ensure sessions meet payer documentation standards - Enforce supervision minute capture for RBT sessions with BCBA oversight - Route missing elements (signatures, goals, treatment plan linkage) for correction before billing

Claims Generation and Reimbursement Automation

- Bundle documented sessions into 837P claims with payer-specific formatting - Submit via the configured clearinghouse or portal and track statuses - Reconcile remittances (835) alongside session and authorization evidence

Audit and Compliance

- Export complete session packets with timestamps, CPT codes, supervision, and signatures - Maintain machine-readable audit trails aligned to payer requirements - Prove claim provenance and documentation coverage 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, sessions, and claim artifacts

Security

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

Webhooks

Optional asynchronous delivery for session documentation status, claim generation, and remittance updates

Latency

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

Throughput

Designed for high-volume scheduling, session 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 commonly used WebABA practice management and EHR workflows, subject to your licensing and entitlements. We scope coverage (e.g., clients, scheduling, session documentation, authorizations, claim assembly and submission, remittance retrieval) during integration assessment.

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

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

Ready to get a real API?