Supergood | PIMSY API

Supergood | PIMSY API

Programmatically access scheduling, client charts, treatment plans, clinical notes metadata, payer authorizations, and claims workflows in PIMSY with a stable REST API. Supergood builds and operates production-grade, unofficial PIMSY integrations so your team can automate behavioral health operations without heavy custom engineering.

PIMSY is an electronic health record (EHR) and practice management system built for behavioral and mental health providers. With an unofficial API, you could synchronize client and provider rosters, create and manage appointments, validate and track authorizations, assemble and submit claims, and export documentation artifacts and audit trails to your data warehouse.

In plain English, PIMSY helps behavioral health organizations manage clients, schedules, documentation, billing, and compliance. An unofficial API from Supergood turns point-and-click workflows into programmatic endpoints: pull the data you need (clients, sessions, authorizations, claims status), and push the actions you want (create appointments, finalize notes, submit claims)—so your tools can work together automatically.

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

  • Pull: Client demographics and insurance, provider rosters, schedules and session statuses, treatment plan summaries, progress note metadata (status, sign-off), payer authorizations and units remaining, claim statuses and ERA summaries, eligibility results
  • Push: New/updated clients from intake, appointments and telehealth sessions, note status transitions (draft → signed/locked), document uploads, claim submissions and batch corrections, payments and write-offs
  • Build: Authorization-aware scheduling, automated intake and reminders, measurement-based care dashboards, claims assembly and reconciliation, analytics pipelines spanning clinical and financial data

Common requests we hear from PIMSY users include needing reliable exports for analytics, easier ways to keep external calendars/CRMs in sync, and programmatic access to authorizations and claims. Some teams also note that portal-first workflows and MFA/SSO make headless automation challenging. Supergood addresses these realities by delivering a hardened API layer tuned for PIMSY’s behavioral health model.

What is PIMSY?

PIMSY provides behavioral health EHR and practice management capabilities for outpatient, residential, and community-based programs. Core workflows include scheduling, client intake, documentation (treatment plans, progress notes, assessments), telehealth, e-prescribing via partners, utilization/authorizations, and integrated billing from charge capture through claim submission and ERA reconciliation.

Core product areas include:

  • Scheduling and session management (individual and group)
  • Client records, demographics, and insurance management
  • Treatment plans, goals/objectives, and progress notes
  • Telehealth scheduling and links
  • E-prescribing (via partnered solutions), labs/documents
  • Authorizations and utilization tracking
  • Billing and claims (837/835), ERA/EDI workflows
  • Reporting, audit trails, and role-based security

Common data entities:

  • Clients (patients) and contacts/guardians
  • Providers/clinicians and clinical programs
  • Appointments/sessions (including telehealth)
  • Treatment plans, goals, and plan reviews
  • Progress notes and clinical documents (signatures, lock status)
  • Authorizations (payer, service code/CPT, units, dates)
  • Insurance policies and payers
  • Claims, service lines, and remittances (ERAs)
  • Locations, groups, and (where applicable) beds/assignments

The PIMSY Integration Challenge

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

  • Portal-first delivery: Scheduling, notes, and billing actions live primarily in web apps or batch exports, not a unified public API
  • MFA/SSO and security controls: Strong authentication and network policies complicate headless automation
  • Batch EDI and timing windows: 837 generation, ERA retrieval, and payer submissions follow batching constraints
  • Clinical compliance: Signed/locked notes and e-signatures require audit trails and immutable status handling
  • Coding and payer nuances: CPT/HCPCS, modifiers, and authorization rules vary by plan and line of business
  • Change management: Form templates, required fields, and coding updates evolve over time

How Supergood Creates PIMSY 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 behavioral health objects (clients, sessions, notes, authorizations, claims) behind stable schemas
  • Aligns with customer entitlements and licensing constraints to ensure compliant access
  • Bridges batch exports and EDI flows with signed URL retrieval and delivery for claims and ERAs

Use Cases

Intake and Scheduling Sync

  • Push new clients from your intake system into PIMSY with demographics and insurance
  • Create appointments (including telehealth links) and keep external calendars in sync
  • Route confirmations and reminders with status updates back to your CRM

Authorization-Aware Scheduling and Eligibility

  • Validate coverage and authorizations before booking sessions
  • Track units remaining to prevent over-utilization and denials
  • Surface payer-specific rules for front desk and care coordinators

Clinical Documentation and QA

  • Pull note metadata and status to power QA workflows
  • Enforce sign/lock steps and attach supporting documents programmatically
  • Export plan and note summaries to analytics pipelines

Claims Generation and Reimbursement Automation

  • Assemble compliant 837P claims from sessions and authorizations
  • Submit via your configured channel (payer portal or clearinghouse) and track statuses
  • Retrieve ERAs and reconcile payments alongside note and authorization evidence

Analytics and Outcomes Reporting

  • Centralize schedules, documentation metadata, and financials in your data warehouse
  • Monitor productivity, utilization, and no-show rates
  • Build measurement-based care and population health dashboards

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_a19f2c",
    "name": "EHR Admin",
    "entitlements": ["scheduling", "clinical", "billing"]
  }
}

Clients

GET /clients: Retrieve client demographics, insurance, and care team context for downstream scheduling, intake, and analytics.

Query parameters

  • name: string (partial match)
  • dob: ISO 8601 date
  • mrn: string
  • updatedSince: ISO 8601 timestamp
  • page, pageSize: integers

Example response

{
  "items": [
    {
      "clientId": "cli_8293fd",
      "mrn": "MRN-102938",
      "firstName": "Avery",
      "lastName": "Nguyen",
      "dob": "1992-06-15",
      "sex": "F",
      "phone": "+1-555-0102",
      "email": "[email protected]",
      "address": {
        "line1": "415 Pine St",
        "city": "Raleigh",
        "region": "NC",
        "postalCode": "27601"
      },
      "primaryProviderId": "prv_41cf92",
      "insurance": [
        {
          "payerId": "payer_bcbs-nc",
          "memberId": "M1234567",
          "planName": "BCBS NC PPO",
          "primary": true
        }
      ],
      "status": "active",
      "createdAt": "2026-01-05T18:22:10Z",
      "updatedAt": "2026-01-20T12:03:49Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Appointments

POST /appointments: Create or update an appointment/session with service details and optional telehealth configuration. Authorization checks are applied when provided.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/appointments \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clientId": "cli_8293fd",
    "providerId": "prv_41cf92",
    "start": "2026-01-21T15:00:00Z",
    "end": "2026-01-21T15:50:00Z",
    "serviceCode": "90834",
    "modifiers": ["GT"],
    "placeOfService": "02", 
    "locationId": "loc_east-clinic",
    "telehealth": {"enabled": true},
    "authorizationId": "auth_7342c1",
    "status": "scheduled",
    "notes": "Weekly therapy session.",
    "referenceId": "ext-cal-88310"
  }'

Example response

{
  "appointmentId": "apt_58d3e0",
  "status": "scheduled",
  "authorizationApplied": {
    "authorizationId": "auth_7342c1",
    "unitsReserved": 1
  },
  "telehealth": {
    "enabled": true,
    "joinUrl": "https://signed.supergood.ai/tel/abc123..."
  },
  "createdAt": "2026-01-19T15:02:02Z",
  "referenceId": "ext-cal-88310"
}

Authorizations

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

Query parameters

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

Example response

{
  "items": [
    {
      "authorizationId": "auth_7342c1",
      "authorizationNumber": "BH-2026-11872",
      "clientId": "cli_8293fd",
      "clientName": "Avery Nguyen",
      "providerId": "prv_41cf92",
      "payerId": "payer_bcbs-nc",
      "serviceCode": "90834",
      "modifiers": ["GT"],
      "unitsAuthorized": 24,
      "unitsUsed": 8,
      "unitsRemaining": 16,
      "startDate": "2026-01-01",
      "endDate": "2026-06-30",
      "status": "active"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Claims

POST /claims: Assemble an 837P claim from completed sessions. Supergood normalizes service lines and can route the generated file to the configured submission channel.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/claims \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "claimType": "837P",
    "payerId": "payer_bcbs-nc",
    "billingProvider": {
      "npi": "1234567890",
      "name": "Horizon Behavioral Health",
      "billingAddress": {
        "line1": "100 Care Way",
        "city": "Raleigh",
        "region": "NC",
        "postalCode": "27601"
      }
    },
    "subscriber": {
      "memberId": "M1234567",
      "relationship": "self"
    },
    "serviceLines": [
      {
        "appointmentId": "apt_58d3e0",
        "serviceCode": "90834",
        "modifiers": ["GT"],
        "diagnosisCodes": ["F41.1"],
        "units": 1,
        "chargeAmount": 120.00,
        "placeOfService": "02"
      }
    ],
    "submissionChannel": "clearinghouse",
    "referenceId": "billing-batch-jan21"
  }'

Example response

{
  "claimId": "clm_71af2b",
  "status": "queued",
  "edi": {"format": "837P", "size": 41280},
  "submissionChannel": "clearinghouse",
  "createdAt": "2026-01-21T16:05:42Z",
  "reviewUrl": "https://download.pimsy.example/signed/def456...",
  "referenceId": "billing-batch-jan21"
}

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, schedules, notes metadata, authorizations, and claim artifacts
  • Security: Encrypted transport, scoped tokens, and audit logging; respects PIMSY entitlements and compliance requirements
  • Webhooks: Optional asynchronous delivery for schedule changes, claim generation, and remittance updates

Performance Characteristics

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

  1. Supergood Builds and Validates Your API

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

  1. Deploy with Monitoring

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

Schedule Integration Call →


Frequently Asked Questions

Q: Which PIMSY products can this integration cover?

Supergood supports workflows across commonly used PIMSY scheduling, client charting, authorization tracking, and billing tools, subject to your licensing and entitlements. We scope coverage (e.g., appointments, note metadata, authorizations, claims/ERAs) 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 EDI timing windows, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically.

Q: Can I generate claims directly from completed sessions and track remittances?

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


DrFirst API - Programmatically access e-prescribing workflows with Supergood

Waystar API - Revenue cycle automation for eligibility, claims, and ERAs


Ready to automate your PIMSY workflows?

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

Get Started →

Read more