Back to Platform API Guides
HealthcarePartner API only· workaround available

Change Healthcare (Optum) API

Change Healthcare's API access now requires a formal partner agreement and elevated security review following the 2024 cyberattack. Many health systems are actively building backup integration paths. Integuru can generate a production-ready HTTP API. Chat with us to get started.

Backed byY CombinatorFree sandbox trial before production

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on production plans

$0

Sandbox trial before production

What Change Healthcare (Optum) currently offers publicly

Partner API only

Change Healthcare, now operating under Optum following its UnitedHealth Group acquisition, requires a formal partner agreement and an elevated security review before API access is granted. The February 2024 cyberattack, the largest healthcare data breach in US history, resulted in significantly tightened access controls. Development teams must complete a formal partner onboarding process, pass a security assessment, and satisfy Optum's partner requirements before receiving production credentials. There is no self-serve developer path, and the security review adds a timeline dependency beyond the standard partner enrollment.

Change Healthcare (Optum) official site

How Integuru fills the gap

Integuru generates a production-ready HTTP API for Change Healthcare (Optum) without a partner agreement. It maps the authenticated network requests the Change Healthcare (Optum) web app already makes, handles the login flow including 2FA, covers the branching states real accounts hit, and keeps the API running with 24/7 on-call maintenance on production plans.

Planned endpoints

Actions Integuru could expose

Final scope is confirmed when the integration is built
submit_claim

Submit a professional or institutional claim through Change Healthcare's clearinghouse to the designated payer

get_claim_status

Retrieve the current processing status of a submitted claim including payer acknowledgment, adjudication status, and rejection codes

list_claims

Return a paginated list of claims filtered by date range, payer, provider, and claim status

check_eligibility

Submit a real-time eligibility inquiry for a patient against a specified payer through the Change Healthcare network

get_eligibility_response

Retrieve the eligibility response for a patient including coverage details, deductible balances, copay amounts, and in-network status

submit_prior_auth

Initiate a prior authorization request through Change Healthcare's PA network for a procedure or service

get_prior_auth_status

Retrieve the current status of a prior authorization request including payer decision, denial reason, and reference number

get_remittance_advice

Retrieve remittance advice for a claim batch including payment amounts, adjustment codes, and denial reasons

list_payments

List electronic remittance payments received from payers via Change Healthcare with deposit dates and payment totals

get_patient_balance

Retrieve the outstanding patient responsibility balance for a claim after payer adjudication and remittance posting

...many more

These actions reflect what Integuru would generate based on the workflows Change Healthcare (Optum) exposes through its web interface.

Need a different Change Healthcare (Optum) action?

Tell us the workflows and accounts you need. Requested integrations are delivered to a sandbox you can test free before production.

Process

What happens after you book a call

  1. 1Tell us the Change Healthcare (Optum) workflows you need

    Book a call and list the actions, account types and call volume. There is no separate build fee to start.

  2. 2Integuru builds the API in days

    The team maps the authenticated requests Change Healthcare (Optum) makes into a direct HTTP API, covering the edge cases you named, and delivers it to a sandbox you test free.

  3. 3Move to production, maintained

    Call documented REST endpoints from your stack, and hand breakage to Integuru: production integrations are maintained around the clock, with auth auto-healing included.

Guide

Change Healthcare (Optum) integration guide

Overview

Change Healthcare is one of the largest healthcare clearinghouses and technology companies in the United States, processing billions of clinical and financial transactions annually between providers, payers, and pharmacy networks. The company is now operating under Optum following its acquisition by UnitedHealth Group, and its network spans claims submission, eligibility verification, prior authorization, and remittance advice across the commercial insurance, Medicare, Medicaid, and pharmacy benefit markets. The scale of Change Healthcare's transaction volume means that a health system or mid-to-large physician group is almost certainly routing some portion of its claims through the Change Healthcare network, making it a required integration for many RCM and billing automation products.

The February 2024 cyberattack changed the access picture materially. The incident, widely described as the largest healthcare data breach in US history, disrupted claims processing for weeks across thousands of provider organizations and exposed the risks of concentrated dependency on a single clearinghouse. In the aftermath, Change Healthcare tightened its partner access requirements: API access now requires a formal partner agreement plus an elevated security review that goes beyond the standard enrollment. Development teams that previously relied on less formal integration paths or were mid-enrollment when the breach occurred now face a more involved process to receive production credentials. There is no self-serve developer path.

Many health systems responded to the outage by actively seeking backup integration paths. Legal and compliance teams at provider organizations are now evaluating whether concentrating all clearinghouse transactions through a single partner agreement represents an acceptable operational risk. For healthtech companies building RCM, eligibility, or remittance tools, this environment creates both urgency around the Change Healthcare integration and demand from health system customers for alternatives they can fall back on.

Integuru generates a production-ready HTTP API for Change Healthcare using direct HTTP requests against the same endpoints the Change Healthcare web application uses internally. Claims submission, eligibility verification, prior authorization tracking, and remittance data are all reachable through Integuru's API without a formal partner agreement and security review gating the build. The Production plan's 24/7 on-call maintenance team handles session management, re-authentication, and endpoint changes. Integuru can be deployed in HIPAA-compliant environments; discuss your compliance requirements when you chat with us.


Why Teams Need This Integration

Change Healthcare's clearinghouse volume and its concentration in the hospital and health system market make it a non-optional integration for most RCM-adjacent products. The post-breach partner program and the backup-path demand from health system customers make the case for building through Integuru even stronger than it was before 2024.

RCM platforms and billing automation tools for hospitals. Hospital billing teams and revenue cycle automation products that process claims through Change Healthcare need programmatic access to submit_claim, get_claim_status, and list_claims across high encounter volumes. For a billing platform serving multiple health systems, the partner security review is a per-organization dependency that serializes the integration rollout. Integuru's per-account authentication model handles multiple health system instances without a separate partner review for each one.

Backup clearinghouse integration for health system compliance requirements. Following the February 2024 breach, legal and compliance teams at health systems are actively addressing the risk of single-clearinghouse concentration. A health system whose primary clearinghouse relationship runs through Change Healthcare needs a backup path that can be activated if the primary channel experiences another disruption. Integuru provides that path: claims, eligibility, and remittance actions that function as a live API without depending on the same partner agreement channel as the primary integration.

Eligibility verification and real-time coverage tools. check_eligibility and get_eligibility_response surface real-time eligibility data from payers on the Change Healthcare network, returning coverage details, deductible balances, and copay amounts for patient access tools, scheduling platforms, and front-desk automation products. The breach-related outage in 2024 disrupted eligibility verification at thousands of provider locations, creating visible demand for alternative eligibility paths alongside the primary clearinghouse relationship.

Remittance reconciliation and payment analytics. get_remittance_advice and list_payments retrieve remittance data from payers transacting through Change Healthcare, including payment amounts, adjustment codes, and denial reasons. Revenue cycle analytics platforms that need to reconcile payments across clearinghouses require Change Healthcare remittance data to close the revenue loop for health system customers.


RCM Workflows This Integration Covers

The ten planned actions span the core revenue cycle workflows that Change Healthcare manages between providers and payers:

  • Claims management: submit_claim sends professional and institutional claims through Change Healthcare's clearinghouse to the designated payer. get_claim_status retrieves adjudication status and rejection codes. list_claims returns paginated claim records filtered by date, payer, provider, and status.
  • Eligibility verification: check_eligibility submits a real-time inquiry for a patient against a specified payer. get_eligibility_response returns coverage details, deductible balances, copay amounts, and in-network status for the patient's active plan.
  • Prior authorization: submit_prior_auth initiates a PA request through Change Healthcare's network for a procedure or service. get_prior_auth_status returns the authorization decision including approval, denial reason, and payer reference number.
  • Remittance and payments: get_remittance_advice retrieves remittance batches with payment amounts, adjustment codes, and denial reasons. list_payments surfaces electronic remittance payments with deposit dates and totals.
  • Patient financial data: get_patient_balance retrieves the outstanding patient responsibility after payer adjudication and remittance posting.

Adjacent Integrations

Integuru already covers several of the EHR platforms whose health system and physician group customers route claims through Change Healthcare. The athenahealth integration guide addresses the MDP partner program barrier for one of the most common EHR platforms connected to Change Healthcare's clearinghouse, with eleven planned actions spanning patient records, clinical notes, and billing data. The Kareo integration guide addresses the billing and clinical workflow gap for independent practices on Tebra. The Modmed integration is the most complete EHR integration on Integuru today, with 21 live actions spanning claims, payments, insurance policies, and full patient management.

Live in Healthcare

Integuru already supports these platforms in the same vertical

Live, production-ready integrations, not requests

Good to know

Before you book a call

How long does this take?
Most managed-service integration requests are built within a few days, including the workflows and edge cases you ask for.
What if Change Healthcare (Optum) changes or breaks?
Every managed integration includes 24/7 on-call maintenance, so your team is never pulled into patching target-platform changes.
What does it cost?
You test the Change Healthcare (Optum) integration free in a sandbox before paying anything. Production pricing follows the standard Production plan (starts at $499/month, including 24/7 on-call maintenance), scoped to the platforms, workflows and call volume you need.

FAQ

Frequently asked questions