How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Stedi Coordination of benefits API

The Coordination of benefits API from Stedi — 1 operation(s) for coordination of benefits.

Stedi Coordination of benefits API is one of 25 APIs that Stedi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Coordination of benefits. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 1 operation across 1 path, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 2024-04-01.

Requests are made against 2 base URLs: https://healthcare.us.stedi.com/2024-04-01, https://healthcare.us.stedi.com/2026-06-01.

1 operations 1 paths 42 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2024-04-01
Base URL
https://healthcare.us.stedi.com/2024-04-01
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Stedi Coordination of benefits API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (httpApiKeyAuth). By default, every request must be authenticated.

  • httpApiKeyAuth — A [Stedi API Key](https://portal.stedi.com/app/settings/api-keys) for authentication.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Coordination of benefits 1
POST
/coordination-of-benefits
Submit a coordination of benefits (COB) check in JSON format
CoordinationOfBenefits body → 200400403404429500503504

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are COBResponseDependent (13 properties), COBResponseSubscriber (11 properties), CoordinationOfBenefitsResponseContent (9 properties), COBBenefitsRelatedEntity (7 properties). Each schema is shown below with its type and property counts.

COBMetaData
object
3 properties
COBPlanDateInformation
object
Dates associated with the patient's health plan coverage. This information is used to determine their eligibility for benefits. - The provided dates apply to e…
2 properties
COBResponseServiceTypeCode
string
Code identifying the type of services included in a benefitsInformation object.
COB
object
5 properties
EligibilityCheckFollowupAction
string
Payers may sometimes return other non-compliant values.
COBResponseBenefitsInformationCode
string
The code indicating the type of benefits information. Can be 1 - Active Coverage, 6 - Inactive, R - Other or Additional Payor, or V - Cannot Process.
EntityIdentifierName
string
Identifies the type of benefitsInformation[].benefitsRelatedEntities.
AccessDeniedExceptionResponseContent
object
The server response for authorization failure.
2 properties 1 required
COBDependent
object
A dependent for which you want to check coordination of benefits. - An individual qualifies as a dependent when they are listed as a dependent on the subscribe…
4 properties 3 required
EntityIdentificationCode
string
Code identifying the type of entityIdentificationValue.
COBResponseServiceTypeCodeName
string
The names of the benefitsInformation[].serviceTypeCodes included in the response.
GatewayTimeoutExceptionResponseContent
object
The server response for a gateway timeout error.
2 properties 1 required
BadRequestException
object
The server cannot process the request due to an apparent client error.
2 properties 1 required
ServiceUnavailableExceptionResponseContent
object
The server is temporarily unavailable.
2 properties 1 required
EligibilityCheckError
object
When a payer rejects your eligibility check, the response contains one or more AAA errors that specify the reasons for the rejection and any recommended follow…
6 properties
EligibilityCheckErrorCode
string
This is a superset of all the possible codes in the sub-loops, as all errors are bubbled up to the top level of the response Payers may sometimes return other…
CoordinationOfBenefits400ErrorResponseContent
COBBenefitsInformationName
string
The full name of the benefits information code.
InternalFailureExceptionResponseContent
object
The server response when an unexpected error occurred while processing request.
2 properties 1 required
ValidationException
object
A standard error for input validation failures. This should be thrown by services when a member of the input structure falls outside of the modeled or document…
2 properties 1 required
Address
object
7 properties
COBResponseSubscriber
object
Information about the primary policyholder for the insurance plan listed in the COB request.
11 properties
ResponseStateOrProvinceCode
string
The US state or Canadian province code with unknown option. For example, TN for Tennessee or NB for New Brunswick. Payers may sometimes return other non-compli…
COBServiceTypeCode
string
The service type code for the encounter. If not provided, the default value is 30.
ValidationExceptionField
object
Describes one specific validation failure for an input member.
2 properties 2 required
COBBenefitsInformation
object
7 properties
ThrottlingExceptionResponseContent
object
The server response when usage plan or account-level throttling limits exceeded.
2 properties 1 required
GenderWithUnknown
string
RelationToSubscriberCodeName
string
The name of the relationToSubscriberCode.
CoordinationOfBenefitsResponseContent
object
9 properties
COBEncounter
object
Information about the encounter. - You can submit COB checks with the 30 service type code for Health Benefit Plan Coverage. This is the broadest service type…
4 properties
COBPayer
object
2 properties
COBProvider
object
Information about the entity requesting the coverage.
4 properties 1 required
COBResponseBenefitsInformationSubscriber
object
1 property
COBResponseDependent
object
Information about the dependent listed in the original COB request.
13 properties
RelationToSubscriberCode
string
The code indicating the dependent's relationship to the subscriber.
ResourceNotFoundExceptionResponseContent
object
The server response when the specified resource cannot be found after an API request passes authentication and authorization.
2 properties 1 required
COBResponseProvider
object
Information about the entity that submitted the original eligibility check request. This may be an individual practitioner, a medical group, a hospital, or ano…
5 properties
CoordinationOfBenefitsRequestContent
object
5 properties 4 required
COBSubscriber
object
The primary policyholder for the insurance plan or a dependent with a unique member ID. If a dependent has a unique member ID, include their information here a…
5 properties 3 required
COBBenefitsDateInformation
object
Dates associated with the benefits. Dates listed only apply to the benefitsInformation object in which this benefitsDateInformation is provided.
6 properties
COBBenefitsRelatedEntity
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stedi-coordination-of-benefits-api-openapi.yml Raw ↑

Other APIs Stedi publishes across the network.

Stedi Claim acknowledgments API
Stedi Claim Attachments API
Stedi Claim submission API
Stedi Documents API
Stedi Enrollments API
Stedi Events API
Stedi Executions API
Stedi Fragments API
Stedi Insurance discovery API
Stedi Partnerships API
Stedi Payer API
Stedi Payers API
Where this information came from

This is an independent, third-party profile of Stedi Coordination of benefits API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.