Introducing Stedi’s CAQH CORE SOAP endpoint for real-time eligibility
Aug 6, 2025
Products
You can now run real-time eligibility checks using our CAQH CORE–compliant SOAP API endpoint.
CAQH CORE SOAP is a widely adopted XML-based interoperability standard for exchanging healthcare transactions, like eligibility checks. It defines how systems can connect and exchange that data in a consistent, reliable way.
If you're already using CAQH CORE SOAP, our SOAP endpoint is the fastest way to start running eligibility checks with Stedi. Just point your existing integration to our endpoint – no other changes are needed.
Most Stedi customers use our JSON API for real-time eligibility. JSON is familiar, fast to integrate, and easy to work with. But if you’ve already built on SOAP, switching to JSON adds unnecessary overhead.
This endpoint removes that step.
The endpoint supports CAQH CORE Connectivity Rule vC2.2.0. We plan to support CAQH CORE Connectivity Rule vC4.0.0 as industry adoption increases.
How it works
To use the endpoint, send a POST request to:
https://healthcare.us.stedi.com/2025-06-01/protocols/caqh-core
In the request body, use the standard CAQH CORE Connectivity Rule vC2.2.0 SOAP envelope. Wrap your X12 270 eligibility request in the Payload element as CDATA. Authenticate with WS-Security headers using your Stedi account ID and Stedi API key.
You can find your Stedi account ID at the end of any Stedi portal URL. For example, in https://portal.stedi.com/app/healthcare/eligibility?account=1111-33333-55555, the account ID is 1111-33333-55555.
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:cor="http://www.caqh.org/SOAP/WSDL/CORERule2.2.0.xsd"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="true" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>STEDI-ACCOUNT-ID</wsse:Username> <wsse:Password>STEDI-API-KEY</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <cor:COREEnvelopeRealTimeRequest> <PayloadType>X12_270_Request_005010X279A1</PayloadType> <ProcessingMode>RealTime</ProcessingMode> <PayloadID>YOUR-PAYLOAD-ID</PayloadID> <TimeStamp>2024-07-29T12:00:00Z</TimeStamp> <SenderID>SENDER-ID</SenderID> <ReceiverID>RECEIVER-ID</ReceiverID> <CORERuleVersion>2.2.0</CORERuleVersion> <Payload><![CDATA[ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231106*1406*^*00501*000000001*0*T*>~GS*HS*SENDERGS*RECEIVERGS*20231106*140631*000000001*X*005010X279A1~ST*270*1234*005010X279A1~BHT*0022*13*10001234*20240321*1319~HL*1**20*1~NM1*PR*2*ABCDE*****PI*11122~HL*2*1*21*1~NM1*1P*2*ACME HEALTH SERVICES*****SV*1999999984~HL*3*2*22*0~TRN*1*11122-12345*1234567890~NM1*IL*1*JANE*DOE****MI*123456789~DMG*D8*19000101~DTP*291*D8*20240108~EQ*MH~SE*13*1234~GE*1*000000001~IEA*1*000000001~]]></Payload> </cor:COREEnvelopeRealTimeRequest> </soapenv:Body> </soapenv:Envelope>
Stedi returns a synchronous XML response containing the X12 271 eligibility response or a 999 acknowledgement, depending on the payer's response.
Try it free
The Real-Time Eligibility Check SOAP endpoint is available on all paid Stedi plans. If you’re not a customer, request a trial. Most teams are up and running in under a day.
You can now run real-time eligibility checks using our CAQH CORE–compliant SOAP API endpoint.
CAQH CORE SOAP is a widely adopted XML-based interoperability standard for exchanging healthcare transactions, like eligibility checks. It defines how systems can connect and exchange that data in a consistent, reliable way.
If you're already using CAQH CORE SOAP, our SOAP endpoint is the fastest way to start running eligibility checks with Stedi. Just point your existing integration to our endpoint – no other changes are needed.
Most Stedi customers use our JSON API for real-time eligibility. JSON is familiar, fast to integrate, and easy to work with. But if you’ve already built on SOAP, switching to JSON adds unnecessary overhead.
This endpoint removes that step.
The endpoint supports CAQH CORE Connectivity Rule vC2.2.0. We plan to support CAQH CORE Connectivity Rule vC4.0.0 as industry adoption increases.
How it works
To use the endpoint, send a POST request to:
https://healthcare.us.stedi.com/2025-06-01/protocols/caqh-core
In the request body, use the standard CAQH CORE Connectivity Rule vC2.2.0 SOAP envelope. Wrap your X12 270 eligibility request in the Payload element as CDATA. Authenticate with WS-Security headers using your Stedi account ID and Stedi API key.
You can find your Stedi account ID at the end of any Stedi portal URL. For example, in https://portal.stedi.com/app/healthcare/eligibility?account=1111-33333-55555, the account ID is 1111-33333-55555.
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:cor="http://www.caqh.org/SOAP/WSDL/CORERule2.2.0.xsd"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="true" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>STEDI-ACCOUNT-ID</wsse:Username> <wsse:Password>STEDI-API-KEY</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <cor:COREEnvelopeRealTimeRequest> <PayloadType>X12_270_Request_005010X279A1</PayloadType> <ProcessingMode>RealTime</ProcessingMode> <PayloadID>YOUR-PAYLOAD-ID</PayloadID> <TimeStamp>2024-07-29T12:00:00Z</TimeStamp> <SenderID>SENDER-ID</SenderID> <ReceiverID>RECEIVER-ID</ReceiverID> <CORERuleVersion>2.2.0</CORERuleVersion> <Payload><![CDATA[ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231106*1406*^*00501*000000001*0*T*>~GS*HS*SENDERGS*RECEIVERGS*20231106*140631*000000001*X*005010X279A1~ST*270*1234*005010X279A1~BHT*0022*13*10001234*20240321*1319~HL*1**20*1~NM1*PR*2*ABCDE*****PI*11122~HL*2*1*21*1~NM1*1P*2*ACME HEALTH SERVICES*****SV*1999999984~HL*3*2*22*0~TRN*1*11122-12345*1234567890~NM1*IL*1*JANE*DOE****MI*123456789~DMG*D8*19000101~DTP*291*D8*20240108~EQ*MH~SE*13*1234~GE*1*000000001~IEA*1*000000001~]]></Payload> </cor:COREEnvelopeRealTimeRequest> </soapenv:Body> </soapenv:Envelope>
Stedi returns a synchronous XML response containing the X12 271 eligibility response or a 999 acknowledgement, depending on the payer's response.
Try it free
The Real-Time Eligibility Check SOAP endpoint is available on all paid Stedi plans. If you’re not a customer, request a trial. Most teams are up and running in under a day.
You can now run real-time eligibility checks using our CAQH CORE–compliant SOAP API endpoint.
CAQH CORE SOAP is a widely adopted XML-based interoperability standard for exchanging healthcare transactions, like eligibility checks. It defines how systems can connect and exchange that data in a consistent, reliable way.
If you're already using CAQH CORE SOAP, our SOAP endpoint is the fastest way to start running eligibility checks with Stedi. Just point your existing integration to our endpoint – no other changes are needed.
Most Stedi customers use our JSON API for real-time eligibility. JSON is familiar, fast to integrate, and easy to work with. But if you’ve already built on SOAP, switching to JSON adds unnecessary overhead.
This endpoint removes that step.
The endpoint supports CAQH CORE Connectivity Rule vC2.2.0. We plan to support CAQH CORE Connectivity Rule vC4.0.0 as industry adoption increases.
How it works
To use the endpoint, send a POST request to:
https://healthcare.us.stedi.com/2025-06-01/protocols/caqh-core
In the request body, use the standard CAQH CORE Connectivity Rule vC2.2.0 SOAP envelope. Wrap your X12 270 eligibility request in the Payload element as CDATA. Authenticate with WS-Security headers using your Stedi account ID and Stedi API key.
You can find your Stedi account ID at the end of any Stedi portal URL. For example, in https://portal.stedi.com/app/healthcare/eligibility?account=1111-33333-55555, the account ID is 1111-33333-55555.
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:cor="http://www.caqh.org/SOAP/WSDL/CORERule2.2.0.xsd"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="true" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>STEDI-ACCOUNT-ID</wsse:Username> <wsse:Password>STEDI-API-KEY</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <cor:COREEnvelopeRealTimeRequest> <PayloadType>X12_270_Request_005010X279A1</PayloadType> <ProcessingMode>RealTime</ProcessingMode> <PayloadID>YOUR-PAYLOAD-ID</PayloadID> <TimeStamp>2024-07-29T12:00:00Z</TimeStamp> <SenderID>SENDER-ID</SenderID> <ReceiverID>RECEIVER-ID</ReceiverID> <CORERuleVersion>2.2.0</CORERuleVersion> <Payload><![CDATA[ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231106*1406*^*00501*000000001*0*T*>~GS*HS*SENDERGS*RECEIVERGS*20231106*140631*000000001*X*005010X279A1~ST*270*1234*005010X279A1~BHT*0022*13*10001234*20240321*1319~HL*1**20*1~NM1*PR*2*ABCDE*****PI*11122~HL*2*1*21*1~NM1*1P*2*ACME HEALTH SERVICES*****SV*1999999984~HL*3*2*22*0~TRN*1*11122-12345*1234567890~NM1*IL*1*JANE*DOE****MI*123456789~DMG*D8*19000101~DTP*291*D8*20240108~EQ*MH~SE*13*1234~GE*1*000000001~IEA*1*000000001~]]></Payload> </cor:COREEnvelopeRealTimeRequest> </soapenv:Body> </soapenv:Envelope>
Stedi returns a synchronous XML response containing the X12 271 eligibility response or a 999 acknowledgement, depending on the payer's response.
Try it free
The Real-Time Eligibility Check SOAP endpoint is available on all paid Stedi plans. If you’re not a customer, request a trial. Most teams are up and running in under a day.
Share
Get started with Stedi
Get started with Stedi
Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.