Register at developer.optum.com and complete the Change Healthcare API onboarding process; obtain OAuth 2.0 client credentials and review the API URLs documentation for the current base URL for the eligibility and claims environment.
Authenticate using the OAuth 2.0 client credentials flow: POST to the token endpoint with your client_id and client_secret using grant_type=client_credentials; include the returned access token as Bearer YOUR_ACCESS_TOKEN in all subsequent API requests.
For professional claims, POST an 837P transaction to the professional claims API endpoint in either JSON or raw X12 format; include the required trading partner ID and submitter ID obtained during enrollment.
Poll the claim acknowledgment endpoint using the returned transaction ID to retrieve the 999 functional acknowledgment indicating whether the EDI envelope was accepted or rejected at the clearinghouse level.
After clearinghouse acceptance, monitor the claim status endpoint for payer-level acknowledgments (277CA) which provide per-claim accepted or rejected status; a 277CA rejection requires claim correction and resubmission.
For batch workflows, use the batch submission endpoint and implement a reconciliation job that matches batch responses back to submitted claims using the payer claim control numbers returned in acknowledgments.
Known gotchas
The Change Healthcare clearinghouse was rebranded under Optum following UnitedHealth Group's acquisition; API base URLs and documentation moved to developer.optum.com — links to legacy apidocs.changehealthcare.com endpoints should be re-verified for current validity.
A successful 999 acknowledgment means the EDI file was structurally valid; it does not mean the payer accepted the claim — always monitor downstream 277CA and 277 claim status separately.
Trading partner IDs in the Optum/Change Healthcare network are not the same as Availity payer IDs or Stedi payer IDs; maintain a clearinghouse-specific payer ID table and do not cross-use them.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp