API Release Notes

Active release

APIVersionRelease DateStatusAPI Reference
Attachments Submission Prior AuthorizationV1October 2026✅Attachments Submission Prior Auth API V1
Prior Authorization FHIR HubV1October 2026✅
PayerListV1September 2025✅PayerList API V1
Dental AttachmentsV1September 2024✅Dental Attachments API V1
EligibilityV3April 2021✅Eligibility API V3
Reports (ERA)V2May 2021✅Responses and Reports API V2
Attachments StatusV1December 2020✅Attachment Status API V1
Attachments RetrievalV1December 2020✅Attachments Retrieval API V1
Professional ClaimsV3April 2019✅Professional Claims API V3
Institutional ClaimsV1November 2019✅Institutional Claims API V1
Claim StatusV2April 2019✅Claim Status API V2
Attachments SubmissionV1November 2019✅Attachment Submission API V1

Change history

APIVersionRelease DateStatusComment
EligibilityV2—❌EOL
ReportsV111-01-2019❌EOL: 06-01-2022
Professional ClaimsV24-01-2019❌—
Professional ClaimsV11-0102019❌—
Claim StatusV101-01-2019❌—
MicroPokitDok API—❌EOL
Payer FinderV108-05-2022❌EOL: 9-9-2024
Dental Benefits Advisor (Beta version)V111-01-2021❌—

Legend

  • ✅: Active
  • ❌: Inactive/Deprecated
  • End-of-life (EOL): End of support

Claims Status v2 includes STC10 and STC11 segments — July 2026

The STC segment contains three iterations of the Health Care Claim Status (C043) composite within STC01; STC10 and STC11 (STC10 and STC11 are used to convey states of the entire claim or a specific service line), which vary by loop. STC10 and STC11 are situational and provide additional status information (secondary and tertiary) when needed.

PayerList v1 includes outages endpoint — April 2026

The PayerList /outages endpoint enables providers comprehensive real-time visibility into payer product outages using the stand-inReason indicator as the primary identification mechanism.

Reports V2 streaming of large files — September 2022

  • 413 response scenarios for large amount of data/reports
  • Streaming and non streaming versus responses to better handle large files from Reports v2

For more information, see 413 response scenario and streaming and non-streaming versus responses.

Eligibility V3 AAAError codes — August 2022

For a list of Eligibility Error messages, error codes, reasons for errors, and their resolutions, see:

📘

NOTE

We do not support the Claim Responses and Reports v1 API. Please start using the Claim Responses and Reports v2 release at your earliest opportunity.

Updated API endpoint URLs

📘

NOTE

Medical Network APIs v1, v2, and v3 (as of 09-02-2021) are now deployed to an enhanced cloud-native network connection, which offers improved API speed and reliability. We recommend updating your systems to the following API endpoint URLs at the first opportunity.

API URLs

See API URLs.

Release notes

Eligibility V3 — 11-30-2020

Eligibility V3 Updates — 11-30-2020
  • Security and authorization changes.
  • Host and URL changes.
  • Deprecated: Accept application/vnd.changehealthcare.medicaleligibility-v2+json header mentioned in v2, there is no need to send or increment; versioning will be managed through the URL path.
  • Documentation updates.

Eligibility V3 Updates — 03-05-2021

Eligibility V3 Updates — 03-05-2021
  • Added two arrays – benefitsRelatedEntities and eligibilityAdditionalInformationList.
    • JSON object in benefitsRelatedEntities maps to objects within Loop 2120C.
    • JSON object in eligibilityAdditionalInformationList maps to objects in Loop 2115C.
Objects in the array will be equal to the number of times the loop repeats.
  • Documentation updates.
  • Security and Authorization changes.
  • 📘

    NOTE

    The legacy benefitsRelatedEntity and eligibilityAdditionalInformation objects are going to be deprecated in the future releases because the information is already captured in objects that are part of their respective arrays.

    Eligibility JSON-to-EDI API Mapping

    DateDescription
    05-17-2019Added field information V1.
    05-10-2021Conversion to Markdown, integration into live documents.
    11-11-2021Various content updates.

    Deprecated

    The Trading Partner ID attribute is no longer used.

    Trading Partner v7 API — August 2023

    The Trading Partner v7 API is no longer supported and API requests will not work from August 15, 2023.


    Did this page help you?