GET /professional-claim-submissions/{id}

Changed on

Retrieve a claim's data and map it to Stedi's CMS-1500 JSON format

Request

  • Base URL
    https://claims.us.stedi.com/2025-03-07
  • URL
    https://claims.us.stedi.com/2025-03-07/professional-claim-submissions/{id}
  • Auth
    API key in header Authorization

Path parameters

idstring required

A unique identifier for a specific submission of a claim within Stedi. Stedi generates a submission ID for the initial submission and then a new submission ID for every resubmission of the same claim. This is different from the claim ID, which doesn't change throughout the claim's lifecycle.

You can retrieve this ID from the submissionId property in the Create Professional Claim JSON endpoint response.

Response

GetProfessionalClaimSubmission 200 response

claimIdstring required

A unique identifier for the claim within Stedi. This ID stays the same throughout the claim's entire lifecycle. For example, the claim ID is the same for the initial submission and any resubmissions. This is how Stedi links a particular claim to responses, such as 277CA claim acknowledgments.

processedAtstring date-time required

The time Stedi processed the submission.

stediPayerIdstring

The payer identifier in Stedi's system.

submissionIdstring required

A unique identifier for a specific submission of a claim within Stedi. Stedi generates a submission ID for the initial submission and then a new submission ID for every resubmission of the same claim. This is different from the claim ID, which doesn't change throughout the claim's lifecycle.

Changes

    • info

      the // response's property pattern was changed from ^\d+(\.\d{1,2})?$ to ^-?\d*\.?\d+$ for the status

    • info

      the // response's property pattern was changed from ^\d+(\.\d{1,2})?$ to ^-?\d*\.?\d+$ for the status

    • info

      the //// response's property pattern was changed from ^\d{1,8}(\.\d{1,3})?$ to ^-?\d*\.?\d+$ for the status

    • info

      the /// response's property pattern was changed from ^\d+(\.\d{1,2})?$ to ^-?\d*\.?\d+$ for the status

    • info

      the //// response's property pattern was changed from ^\d+(\.\d{1,2})?$ to ^-?\d*\.?\d+$ for the status

    • info

      the /// response's property pattern was changed from ^\d{1,8}(\.\d{1,3})?$ to ^-?\d*\.?\d+$ for the status

    • info

      endpoint added