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

Forta Health Payor Provider Credentials API

The payor_provider_credentials API from Forta Health — 2 operation(s) for payor_provider_credentials.

Forta Health Payor Provider Credentials API is one of 34 APIs that Forta Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 4 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against the base URL https://api.prod.fortahealth.com/api/v1/.

4 operations 2 paths 15 schemas 1 DELETE1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.prod.fortahealth.com/api/v1/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Forta Health Payor Provider Credentials API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 4

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

payor_provider_credentials 4
POST
/api/v1/payor_provider_credentials/
Create Payor Provider Credential
create_payor_provider_credential_api_v1_payor_provider_credentials__post body → 201422
GET
/api/v1/payor_provider_credentials/
Fetch Payor Provider Credentials
fetch_payor_provider_credentials_api_v1_payor_provider_credentials__get 3 params → 200422
PATCH
/api/v1/payor_provider_credentials/{payor_provider_credential_id}/
Patch Payor Provider Credential
patch_payor_provider_credential_api_v1_payor_provider_credentials__payor_provider_credential_id___patch 1 param body → 200422
DELETE
/api/v1/payor_provider_credentials/{payor_provider_credential_id}/
Delete Payor Provider Credential
delete_payor_provider_credential_api_v1_payor_provider_credentials__payor_provider_credential_id___delete 1 param → 200422

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are PayorResponse (19 properties), ProviderListResponse (6 properties), PayorProviderCredentialResponse (5 properties), PayorProviderCredentialCreate (4 properties). Each schema is shown below with its type and property counts.

PayorResponse
object
19 properties 3 required
PayorTypeEnum
string
Enum for payor types.
PayorProviderCredentialCreate
object
4 properties 2 required
PayorSectorEnum
string
Enum for payor sectors.
ClientSupervisionCriteria
object
3 properties
BTTypeEnum
string
ProviderListResponse
object
6 properties 6 required
ClinicalStatusEnum
string
ValidationError
object
3 properties 3 required
HTTPValidationError
object
1 property
ServiceCodeTypeEnum
string
OperatorEnum
string
PayorProviderCredentialResponse
object
5 properties 3 required
ClientSupervisionRequirements-Output
object
2 properties 1 required
PayorProviderCredentialPatch
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

forta-health-payor-provider-credentials-api-openapi.yml Raw ↑

Other APIs Forta Health publishes across the network.

Forta Health Assessment Surveys API
Forta Health Behavior API
Forta Health Bt Supervisions API
Forta Health Claim Invoices API
Forta Health Claims API
Forta Health Client Assessments API
Forta Health Client Cohort Assignments API
Forta Health Client Facility Assignments API
Forta Health Client Supervisions API
Forta Health Clients API
Forta Health Cohorts API
Forta Health Email Cron Configs API
Where this information came from

This is an independent, third-party profile of Forta Health Payor Provider Credentials 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.