POST
/
dental-claims
/
raw-x12-submission
cURL
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 is ideal if you have an existing system that generates X12 EDI files and you want to send them through Stedi.
  1. Call this endpoint with a payload in 837 X12 EDI format.
  2. Stedi validates the EDI and sends the claim to the payer.
  3. The endpoint returns a response from Stedi in JSON format containing information about the claim you submitted and whether the submission was successful.
Visit Submit dental claims for a full how-to guide.

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
​
x12
string
required

Response

DentalClaimsRawX12Submission 200 response

​
status
string

The status of the claim submission.

​
controlNumber
string

An identifier for the transaction.

​
tradingPartnerServiceId
string

An ID for the payer you identified in the original claim. This value may differ from the tradingPartnerServiceId you submitted in the original request because it reflects the payer's internal concept of their ID, not necessarily the ID Stedi uses to route requests to this payer.

​
claimReference
object

Information about the claim.

​
errors
object[]

A list of errors. Currently not used.

​
warnings
object[]

A list of warnings.

​
httpStatusCode
enum<string>

A 200 response indicates that Stedi successfully generated the X12 EDI claim format required by the payer. It does not indicate whether the payer has accepted the claim - the payer will respond later with a 277CA containing this information. Learn more about 277CAs. A 400 response indicates one or more problems with the claim data in the request. Examples include missing required fields, invalid values, or incorrect data types. The response includes a message describing the problem.

Available options:
200 OK,
400 BAD_REQUEST
​
meta
object

Metadata from Stedi about the request.

​
editStatus
string

Currently not used.

​
editResponses
object[]

Currently not used.

​
payer
object

Information about the payer for the submitted claim.

​
failure
object

Currently not used.