POST
/
claim-attachments
/
file
curl --request POST \
  --url https://claims.us.stedi.com/2025-03-07/claim-attachments/file \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "contentType": "application/pdf"
}'
{
  "attachmentId": "d3b3e3e3-3e3e-3e3e-3e3e-3e3e3e3e3e3e",
  "uploadUrl": "https://s3.amazonaws.com/bucket/key"
}

This endpoint is in beta and is subject to change.

This endpoint returns a pre-signed URL that you can use to upload a claim attachment file to Stedi. You must complete this step before you can call the Submit Claim Attachment (275) JSON endpoint.

  1. Call this endpoint to initiate the file upload process.
  2. Stedi returns a unique identifier for the attachment file (attachmentId) and a pre-signed URL (uploadURL). Retain the attachmentId so you can use it when submitting the attachment to the payer.

You only need to complete this step when submitting claims through Stedi’s JSON APIs. If your system already generates X12 EDI, you can send attachments directly through the Submit Claim Attachment (275) Raw X12 endpoint instead.

Upload the attachment to Stedi

Use a PUT request to upload the attachment file to the pre-signed URL (uploadURL) in the response. The request must include a Content-Type header that matches the MIME type you specified for the attachment file.

The following example shows how to upload a JPEG attachment:

curl --request PUT \
  --url "<uploadUrl>" \
  --header "Content-Type: image/jpeg" \
  --upload-file /path/to/file.jpeg

Stedi stores uploaded files for 45 days. After that, you must reupload the file before submitting it to the payer.

Submit the attachment to the payer

Once you’ve uploaded the attachment through the provided URL, you can submit it to the payer through the Submit Claim Attachment (275) JSON endpoint.

Authorizations

Authorization
string
header
required

A Stedi API Key for authentication.

Body

application/json

Request a pre-signed URL to upload a claim attachment file.

contentType
enum<string>
required

The MIME type of the attachment file. For example: image/png or application/pdf.

Available options:
application/pdf,
image/tiff,
image/jpeg,
image/jpg,
image/png

Response

201
application/json
CreateClaimAttachmentFile 201 response

Receive the attachment ID and upload URL.

attachmentId
string
required

Unique identifier for this attachment. You will use this ID to associate the attachment file with the claim when you submit it to the payer.

Required string length: 36
uploadUrl
string
required

A pre-signed URL you can use to upload the file with a PUT request. The PUT request must include a Content-Type header that matches the MIME type you specified for the attachment file.

Required string length: 1 - 2000