Lightning Step API
Lightning Step is an all-in-one behavioral health platform that combines a CRM for admissions, an EHR for clinical care, revenue cycle management, and LIA (Lightning Intelligent Assistant), an ISO 42001-certified AI documentation feature. This page is an independent design exercise that asks what a well-designed Lightning Step API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Lightning Step API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Lightning Step product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is Lightning Step?
Lightning Step is an all-in-one behavioral health platform that combines a CRM for admissions, an EHR for clinical care, revenue cycle management, and LIA (Lightning Intelligent Assistant), an ISO 42001-certified AI documentation feature. Founded in 2015 in Houston, Texas, the company acquired ZenCharts and AVA Billing, and merged with Sunwave Health in October 2025, Lightning Step continues to be sold as a distinct product, and the combined network spans more than 3,000 facilities and 34,000+ users.
Lightning Step serves substance abuse treatment centers, behavioral health treatment centers, mental health clinics, and eating disorder treatment centers, from private practices to multi-location enterprises. For those organizations it is the system of record for the admissions pipeline, clinical documentation, utilization review, and claims.
An API for a platform like this would naturally organize around its core data entities:
- Admissions leads and CRM pipeline records
- Patient demographics and program enrollment
- Clinical documentation and treatment plans
- Utilization review and authorization records
- Claims and revenue cycle data
The Lightning Step Integration Challenge
- No developer portal, public API documentation, SDKs, or integration marketplace, the company says its team "uses well-crafted APIs," but those APIs are internal.
- The partners page lists only a handful of vendor-built integrations (Availity, PaySimple, Twilio, Waystar, CallTrackingMetrics, Salesforce, Microsoft BI), anything else requires contacting the company.
- No documented webhooks, no event-driven notification when a lead converts, a note is signed, or a claim changes status.
- Key workflows, admissions, documentation, utilization review, billing, live entirely in the web application, so programmatic access means either vendor engagement or manual exports.
- Behavioral health and SUD records carry HIPAA and 42 CFR Part 2 obligations, so ad-hoc scraping or uncontrolled exports are not a viable path.
What a Lightning Step API Could Look Like
If Lightning Step exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Lightning Step: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould establish an authenticated session with Lightning Step, including MFA handling and automatic session refresh.
Patient Operations
/patientsWould retrieve patient demographics, program enrollment, and admission records.
Admissions CRM
/leadsWould list admissions CRM leads and referral pipeline records with status and source attribution.
Scheduling
/appointmentsWould list scheduled sessions and appointments with provider and status details.
Clinical Documentation
/encountersWould fetch clinical documentation, assessments, progress notes, and treatment plan updates.
Billing
/submit_claimWould submit claims into Lightning Step's revenue cycle workflows and track submission status.
Use Cases
Admissions pipeline automation
- Sync CRM leads and referral data into marketing and analytics tools - Trigger downstream workflows when a lead converts to an admission - Measure conversion rates by referral source in real time
Utilization review and compliance
- Pull documentation and authorization records for UR teams - Flag missing or expiring authorizations before sessions occur - Assemble audit-ready documentation packets automatically
Revenue cycle visibility
- Extract claims data into BI and finance systems - Monitor denials and days-in-AR across programs - Reconcile Lightning Step RCM data with clearinghouse records
Enterprise reporting
- Aggregate census and clinical activity across locations - Replace manual exports with scheduled programmatic syncs - Feed data warehouses without vendor-built connectors
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require managed credential-based login with MFA support;
Connectivity
Would build on REST API over HTTPS
Response format
Normalized JSON schemas across CRM, EHR, and RCM entities
Rate limits
Tuned per tenant to stay within safe platform thresholds
Session management
Would need automatic session refresh and re-authentication on expiry
Data freshness
On-demand fetches with optional scheduled syncs; near real-time
Security
Encryption in transit and at rest; HIPAA-eligible data handling
Webhooks
Latency
Design target: typical reads return in seconds
Throughput
Design target: scales with concurrent managed sessions per facility
Reliability
24/7 monitoring with automated failure detection and recovery
Versioning
Clear versioning and change management would matter as Lightning Step evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Lightning Step product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.