POST
/
dental-claims
/
raw-x12-submission
curl --request POST \
  --url https://healthcare.us.stedi.com/2024-04-01/dental-claims/raw-x12-submission \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "x12": "ISA*00*          *00*          *ZZ*001690149382   *ZZ*STEDITEST      *240630*0847*^*00501*000000001*0*T*>~GS*HC*001690149382*STEDITEST*20240630*084744*000000001*X*005010X224A2~ST*837*3456*005010X224A2~BHT*0019*00*0123*20061123*1023*CH~NM1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~PER*IC*JERRY*TE*7176149999~NM1*40*2*INSURANCE COMPANY XYZ*****46*66783JJT~HL*1**20*1~NM1*85*2*DENTAL ASSOCIATES*****XX*1999999992~N3*234 SEAWAY ST~N4*MIAMI*FL*33111~REF*EI*587654321~HL*2*1*22*1~SBR*P********CI~NM1*IL*1*SMITH*JANE****MI*111223333~NM1*PR*2*INSURANCE COMPANY XYZ*****PI*66783JJT~HL*3*2*23*0~PAT*19~NM1*QC*1*SMITH*TED~N3*236 N MAIN ST~N4*MIAMI*FL*33413~DMG*D8*19920501*M~CLM*26403774*150***11>B>1*Y*A*Y*I~DTP*472*D8*20061029~REF*D9*17312345600006351~NM1*82*1*DOE*JOHN****XX*1999999992~PRV*PE*PXC*1223G0001X~LX*1~SV3*AD>D2150*100****1~TOO*JP*12*M>O~LX*2~SV3*AD>D1110*50****1~SE*31*3456~GE*1*000000001~IEA*1*000000001~"
}'
{
  "status": "SUCCESS",
  "controlNumber": "000000001",
  "tradingPartnerServiceId": "60054",
  "claimReference": {
    "correlationId": "01J1M588QT2TAV2N093GNJ998T",
    "patientControlNumber": "22266555",
    "timeOfResponse": "2024-07-10T22:05:32.203Z",
    "payerId": "60054",
    "formatVersion": "5010",
    "rhclaimNumber": "01J1M588QT2TAV2N093GNJ998T",
    "serviceLines": [
      {
        "lineItemControlNumber": "111222333"
      }
    ]
  },
  "httpStatusCode": "200 OK",
  "meta": {
    "traceId": "b727b8e7-1f00-4011-bc6e-e41444d406d8"
  },
  "payer": {
    "payerName": "Cigna",
    "payerId": "60054"
  }
}

This endpoint sends 837D (dental) claims to payers in raw X12 EDI format. This is ideal if you have an existing system that generates X12 EDI files and you want to send them through Stedi.

  • Call this endpoint with a payload in 837 X12 EDI format.
  • Stedi validates the EDI and sends the claim to the payer.
  • The endpoint returns a response from Stedi in JSON format containing information about the claim you submitted and whether the submission was successful.

​
Identify service lines

A claim can contain multiple service lines. Since the payer may accept, reject, or pay a subset of those lines, you can receive an 835 response that references a patient control number, but only pertains to some of the service lines.

However, the line item control number serves as a unique identifier for each service line in your claim submission. You can set the line item control number in Loop 2400 REF02, when REF01 = 6R. The line item control number appears in the 277CA and 835 ERA responses as the lineItemControlNumber, allowing you to correlate these responses to specific service lines from the original claim. If you don’t set the line item control number for a service line, Stedi uses a random UUID.

Stedi returns service line identifiers in the claimReference.serviceLines object of the synchronous API response.

​
Character restrictions

Only use the following characters as delimiters: ~, *, : and ^. The X12 format doesn’t support using escape sequences, so you can’t include delimiters or special characters as part of the request data. Stedi returns a 400 error if you include restricted characters as anything other than delimiters in the request.

Only use the X12 Basic and Extended character sets in request data. Using characters outside these sets may cause validation and HTTP 400 errors.

Authorizations

​
Authorization
string
header
required

A Stedi API Key for authentication.

Headers

​
Stedi-Transaction-Setting-Id
string

The outbound transaction setting ID. This option only needs to be specified if a non-default release of the Dental Claims guide needs to be used.

Body

application/json

Response

200
application/json
DentalClaimsRawX12Submission 200 response

The response is of type object.