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

Candid Health Service Lines API

The Service Lines API from Candid Health — 4 operation(s) for service lines.

Candid Health Service Lines API is one of 53 APIs that Candid Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 4 paths, and defines 52 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 10 base URLs: https://pre-api.joincandidhealth.com, https://pre-api-staging.joincandidhealth.com, https://sandbox-pre-api.joincandidhealth.com, https://staging-pre-api.joincandidhealth.com, http://localhost:4000, https://api.joincandidhealth.com, https://api-staging.joincandidhealth.com, https://sandbox-api.joincandidhealth.com, https://staging-api.joincandidhealth.com, http://localhost:5050.

5 operations 4 paths 52 schemas 1 DELETE2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.joincandidhealth.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Candid Health Service Lines API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (OAuthScheme).

  • OAuthScheme — OAuth 2.0 authentication

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Service Lines 5
POST
/api/service-lines/v2
Create Service Line
create 1 param body → 200409422
POST
/api/service-lines/v2/universal
Create Professional or Institutional Service Line
create-universal 1 param body → 200409422
PATCH
/api/service-lines/v2/{service_line_id}/universal
Update service line for encounter that may be institutional or professional
update-universal 2 params body → 200403404422
PATCH
/api/service-lines/v2/{service_line_id}
Update Service Line
update 2 params body → 200403404422
DELETE
/api/service-lines/v2/{service_line_id}
Delete Service Line
delete 2 params → 200403404409

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are type_service-lines_v2_ServiceLine (43 properties), type_service-lines_v2_UniversalServiceLineCreateStandalone (24 properties), type_service-lines_v2_UniversalServiceLineUpdate (23 properties), type_service-lines_v2_ServiceLineCreateStandalone (23 properties). Each schema is shown below with its type and property counts.

type_invoices_v2_ClaimInvoiceItemInfo
object
2 properties 1 required
type_commons_RequestValidationError
object
2 properties 1 required
type_service-lines_v2_ServiceIdQualifier
string
type_commons_ClaimId
string
type_commons_OrganizationId
string
type_encounter-providers_v2_ProviderSecondaryIdentification
object
2 properties 1 required
type_commons_PatientExternalId
string
type_invoices_v2_InvoiceItemInfo
object
2 properties 2 required
type_encounter-providers_v2_OrderingProvider
object
6 properties 1 required
type_commons_EntityNotFoundErrorMessage
object
1 property 1 required
type_invoices_v2_InvoiceDestinationMetadata
object
4 properties 3 required
type_service-lines_v2_ServiceLineAdjustment
object
5 properties 1 required
type_encounter-providers_v2_EncounterProvider
object
11 properties 3 required
type_commons_DateRangeOptionalEnd
object
2 properties 1 required
type_encounter-providers_v2_ProviderSecondaryIdentificationQualifier
string
type_commons_ServiceLineUnits
string
type_invoices_InvoiceStatus
string
type_commons_ProcedureModifier
string
type_commons_QualifierCode
string
type_service-lines_v2_DrugIdentification
object
8 properties 4 required
type_commons_Decimal
string
String representation of a Decimal that can be parsed by most libraries.
type_commons_InvoiceId
string
type_invoices_v2_ServiceLineInvoiceItem
object
2 properties 2 required
type_commons_BillingProviderCommercialLicenseType
string
type_invoices_v2_InvoiceStatus
string
type_service-lines_v2_ServiceLineDenialReason
object
The reason a given service line was denied within a given time range. A service line may be denied for different reasons over time, but only one reason at a ti…
1 property
type_service-lines_v2_ServiceLineUpdate
object
22 properties
type_service-lines_v2_TestResult
object
2 properties 2 required
type_service-lines_v2_UniversalServiceLineUpdate
object
23 properties
type_diagnoses_DiagnosisId
string
type_commons_State
string
type_invoices_v2_Invoice
object
12 properties 9 required
type_commons_EntityConflictErrorMessage
object
1 property 1 required
type_encounter-providers_v2_ProviderId
string
type_invoices_InvoiceItem
object
2 properties 2 required
type_service-lines_v2_ServiceLine
object
43 properties 8 required
type_commons_ServiceLineId
string
type_invoices_v2_InvoiceDestination
string
type_commons_UnauthorizedErrorMessage
object
1 property
type_service-lines_v2_MeasurementUnitCode
string
type_commons_StreetAddressLongZip
object
6 properties 5 required
type_commons_FacilityTypeCode
string
Box 24B on the CMS-1500 claim form. Line-level place of service is not currently supported. 02 for telemedicine, 11 for in-person. Full list here: https://www.…
type_service-lines_v2_UniversalServiceLineCreateStandalone
object
24 properties 3 required
type_service-lines_v2_DenialReasonContent
string
type_invoices_v2_UnattributedInvoiceItem
object
1 property 1 required
type_commons_Date
string
ISO 8601 date; formatted YYYY-MM-DD (i.e. 2012-02-01)
type_invoices_v2_InvoiceInfo
object
3 properties 3 required
type_service-lines_v2_TestResultType
string
type_service-lines_v2_ServiceLineCreateStandalone
object
23 properties 4 required
type_invoices_Invoice
object
13 properties 10 required
type_invoices_v2_ClaimInvoiceItem
object
2 properties 2 required
type_service-lines_v2_ServiceLineERAData
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

candid-health-service-lines-api-openapi.yml Raw ↑

Other APIs Candid Health publishes across the network.

Candid Health Patient Collections API
Candid Health Charge Capture API
Candid Health Exports API
Candid Health Patients API
Candid Health Credentialing API
Candid Health Auth API
Candid Health Default API
Candid Health Diagnoses API
Candid Health Appointments API
Candid Health Billing Notes API
Candid Health Charge Capture Claim Creation API
Candid Health Charge Captures API
Where this information came from

This is an independent, third-party profile of Candid Health Service Lines 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.