Claims Responses and Reports V2 Getting Started

Claims Responses and Reports API

Access all your Professional Claims and Institutional Claims files using Change Healthcare's Claims Responses and Reports API.

The Claims Responses and Reports API provides a direct connection to your mailbox where payers will send their final claims responses and reports. Use this API to access your mailbox for all the files containing complete information about claim payments, claim status updates, and other communications regarding revenue cycles and adjudication from the payer.

Version 2 of this API offers significant improvements to the developer seeking to implement file-fetching and EDI content conversion capabilities to their users' medical transaction console:

*A fully updated OpenAPI 3.0 JSON spec with extensive annotation supporting medical coding and explanation of relationships between JSON attributes and the EDI loops and segment that affect those attributes

  • Rewritten JSON specifications for clarity and understandability
  • Renamed ServiceDetails object to serviceLines to match our other APIs
  • Updates to support a new 'transactions' JSON object for the /835 and /277 endpoints. It lists out each 277 or 835 transaction contained within the report, each with all claims and service lines, when multiple transactions are completed by the payer.

This API is complementary to other Claims APIs such as Claims Status, Institutional Claims and Professional Claims. For example, the Change Healthcare Claims Status API provides status summaries of a claim; it does not download the actual claim data.



You can use this API with your contracted APIs at no additional cost.

We recommend using this API along with your main Claims API to give you the complete basic functionality to manage your professional or institutional claims. Typically, you will need a suite of three Change Healthcare APIs to do your most effective Claims work:

Reporting for Multiple Claims

Our Claims Responses and Reports v2 API supports the combination and reception of multiple Professional or Institutional claims in a single 277 or 837 report.



  • If you only plan to use a few daily transactions, you can use our ConnectCenter for your Medical Network transaction needs.
    It provides most of the features supported by an API console but only allows manual entry for all data needed for a transaction. It contains Change Healthcare’s Payer Lists, the Payer List Enrollments wizard, and other API customer resources.
  • For providers sending hundreds of daily requests, we recommend using our APIs to be able to automate the submission processes and have a better fit for your business needs.

Did this page help you?