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 Provider Credentialing Span API

The Provider Credentialing Span API from Candid Health — 4 operation(s) for provider credentialing span.

Candid Health Provider Credentialing Span 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 Provider Credentialing Span. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 4 paths, and defines 38 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.

10 operations 4 paths 38 schemas 2 DELETE4 GET2 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 Provider Credentialing Span API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (OAuthScheme).

  • OAuthScheme — OAuth 2.0 authentication

Paths & Operations 10

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

Provider Credentialing Span 10
POST
/api/provider-credentialing-span/v2/facility
Create facility credentialing span
createFacility 1 param body → 200403422
GET
/api/provider-credentialing-span/v2/facility
Get all facility credentialing spans
getAllFacilities 6 params → 200403422
GET
/api/provider-credentialing-span/v2/facility/{facility_credentialing_id}
Get facility credentialing span
getFacility 2 params → 200403404
DELETE
/api/provider-credentialing-span/v2/facility/{facility_credentialing_id}
Delete facility credentialing span
deleteFacility 2 params → 200403404
PATCH
/api/provider-credentialing-span/v2/facility/{facility_credentialing_id}
Update facility credentialing span
updateFacility 2 params body → 200403404422
POST
/api/provider-credentialing-span/v2
Create provider credentialing span
create 1 param body → 200403422
GET
/api/provider-credentialing-span/v2
Get all provider credentialing spans
getAll 7 params → 200403422
GET
/api/provider-credentialing-span/v2/{provider_credentialing_id}
Get provider credentialing span
get 2 params → 200403404
DELETE
/api/provider-credentialing-span/v2/{provider_credentialing_id}
Delete provider credentialing span
delete 2 params → 200403404
PATCH
/api/provider-credentialing-span/v2/{provider_credentialing_id}
Update provider credentialing span
update 2 params body → 200403404422

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are type_organization-service-facilities_v2_OrganizationServiceFacility (16 properties), type_organization-providers_v3_OrganizationProviderV2 (15 properties), type_credentialing_v2_ProviderCredentialingSpan (13 properties), type_credentialing_v2_FacilityCredentialingSpan (10 properties). Each schema is shown below with its type and property counts.

type_organization-service-facilities_v2_OrganizationServiceFacility
object
16 properties 5 required
type_credentialing_v2_ProviderCredentialingSpanId
string
type_commons_PageToken
string
type_organization-providers_v2_ProviderType
string
type_commons_RequestValidationError
object
2 properties 1 required
type_organization-providers_v2_LicenseType
string
type_organization-service-facilities_v2_ServiceFacilityStatus
string
type_credentialing_v2_CredentialingSpanStatus
string
Stage of a credentialing span in the credentialing workflow.
type_organization-providers_v3_OrganizationProviderV2
object
15 properties 7 required
type_identifiers_IdentifierValue
type_commons_UnprocessableEntityErrorMessage
object
1 property
type_commons_EntityNotFoundErrorMessage
object
1 property 1 required
type_commons_DateRangeOptionalEnd
object
2 properties 1 required
type_organization-service-facilities_v2_ServiceFacilityOperationalStatus
string
type_commons_Regions
type_identifiers_IdentifierCode
string
type_commons_ProviderCredentialingSpanId
string
type_identifiers_IdentifierId
string
type_organization-service-facilities_v2_ServiceFacilityPhysicalType
string
type_organization-providers_v2_OrganizationProviderId
string
type_identifiers_Identifier
object
4 properties 3 required
type_credentialing_v2_FacilityCredentialingSpanPage
object
3 properties 1 required
type_payers_v3_Payer
object
8 properties 3 required
type_organization-service-facilities_v2_ServiceFacilityMode
string
type_organization-service-facilities_v2_ServiceFacilityType
string
type_commons_State
string
type_credentialing_v2_FacilityCredentialingSpan
object
10 properties 6 required
type_credentialing_v2_ProviderCredentialingSpan
object
13 properties 8 required
type_organization-providers_v2_AddressType
string
type_commons_UnauthorizedErrorMessage
object
1 property
type_commons_StreetAddressLongZip
object
6 properties 5 required
type_credentialing_v2_FacilityCredentialingSpanId
string
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_credentialing_v2_ProviderCredentialingSpanPage
object
3 properties 1 required
type_commons_Date
string
ISO 8601 date; formatted YYYY-MM-DD (i.e. 2012-02-01)
type_organization-service-facilities_v2_OrganizationServiceFacilityId
string
type_organization-providers_v2_OrganizationProviderAddress
object
2 properties 2 required
type_payers_v3_PayerUuid
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

candid-health-provider-credentialing-span-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 Provider Credentialing Span 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.