GET
/
export
/
{transactionId}
/
1500
/
pdf
This is a BETA endpoint. We may make backwards incompatible changes.

This endpoint retrieves the NUCC 1500 Claim Form PDF that Stedi automatically generates for submitted 837 professional claims. You can also review and download the PDF from the transaction’s details page in Stedi.

Generation notes

You should be aware of the following behavior and recommendations if you plan to send the generated PDFs to payers or retain them for your records:

The PDF may truncate claim data.

The maximum length for many fields in the 1500 claim form is less than the maximum length for the corresponding properties in the claim request.

Recommendation: Ensure that your claim data is within the maximum length for claim form fields. We especially recommend using USPS abbreviations to avoid truncated addresses in the generated PDF.

The PDF may omit the second line of some addresses.

Some NUCC 1500 items contain address fields that can only be mapped to a single address line. So if you include the address2 JSON property (X12 EDI N302) in your claim submission, that information may not appear in the PDF.

Recommendation: Put all street address line data into the address1 JSON property (X12 EDI N301), ensuring that you adhere to the claim form length constraints.

The PDF won’t populate Item 7 when the patient is a dependent.

Stedi validates the claim data you submit to the API and uses it to generate a compliant X12 EDI transaction to send to the payer. The PDF is generated from the final X12 EDI transaction.

The X12 EDI standard specifies that claims should only contain the insured’s address when the patient is the subscriber. To maintain compliance, Stedi doesn’t include the insured’s address information in the generated X12 EDI transaction when the patient is a dependent, even if you provided the subscriber’s address in the original API request. Since this address information isn’t present in final X12 EDI claim, it’s also not added to Item 7 (Insured’s Address) in the generated PDF.

Authorizations

Authorization
string
header
required

A Stedi API Key for authentication.

Path Parameters

transactionId
string
required

A unique identifier for the processed claim within Stedi. This ID is included in the transaction processed event for the claim, which you can receive automatically through Stedi webhooks. You can also retrieve this ID through the Poll Transactions endpoint or from the transaction's details page within the Stedi app.

Response

200 - application/octet-stream

A base64 encoded string of the CMS-1500 Claim Form PDF. To render the PDF, you must decode the base64 string and save it to a file with a .pdf extension.