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 API

The payor API from Forta Health — 6 operation(s) for payor.

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

Tagged areas include payor. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 9 operations across 6 paths, and defines 22 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/.

9 operations 6 paths 22 schemas 1 DELETE2 GET2 PATCH3 POST1 PUT

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 API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 9

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

payor 9
GET
/api/v1/payors/
Get Payors
get_payors_api_v1_payors__get → 200
POST
/api/v1/payors/
Create Payor
create_payor_api_v1_payors__post body → 201422
GET
/api/v1/payors/{payor_id}
Get Payor
get_payor_api_v1_payors__payor_id__get 1 param → 200422
PUT
/api/v1/payors/{payor_id}
Update Payor
update_payor_api_v1_payors__payor_id__put 1 param body → 200422
POST
/api/v1/payors/{payor_id}/contracts/
Create Payor Contract
create_payor_contract_api_v1_payors__payor_id__contracts__post 1 param body → 201422
PATCH
/api/v1/payors/{payor_id}/contracts/{contract_id}
Update Payor Contract
update_payor_contract_api_v1_payors__payor_id__contracts__contract_id__patch 2 params body → 200422
DELETE
/api/v1/payors/{payor_id}/contracts/{contract_id}
Delete Payor Contract
delete_payor_contract_api_v1_payors__payor_id__contracts__contract_id__delete 2 params → 200422
POST
/api/v1/payors/{payor_id}/service_code_descriptions/
Create Service Code Description
create_service_code_description_api_v1_payors__payor_id__service_code_descriptions__post 1 param body → 201422
PATCH
/api/v1/payors/{payor_id}/service_code_descriptions/{service_code_description_id}/
Update Service Code Description
update_service_code_description_api_v1_payors__payor_id__service_code_descriptions__service_code_description_id___patch 2 params body → 200422

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are PayorDetailedResponse (21 properties), PayorPatch (17 properties), PayorCreate (17 properties), PayorListResponse (9 properties). Each schema is shown below with its type and property counts.

ClientSupervisionCriteria
object
3 properties
ClientSupervisionRequirements-Output
object
2 properties 1 required
PayorServiceCodeDescriptionResponse
object
5 properties 5 required
PayorContractPatch
object
3 properties 2 required
PayorPatch
object
17 properties 8 required
PayorSectorEnum
string
Enum for payor sectors.
BTTypeEnum
string
PayorListResponse
object
9 properties 3 required
HTTPValidationError
object
1 property
ServiceCodeTypeEnum
string
PayorServiceCodeDefaultDescriptionResponse
object
5 properties 3 required
PayorTypeEnum
string
Enum for payor types.
ClientSupervisionRequirements-Input
object
2 properties 1 required
PayorCreate
object
17 properties 8 required
ValidationError
object
3 properties 3 required
PayorServiceCodeDescriptionCreate
object
2 properties 2 required
ServiceCodeEnum
string
OperatorEnum
string
PayorContractResponse
object
5 properties 4 required
PayorContractCreate
object
4 properties 3 required
PayorServiceCodeDescriptionPatch
object
1 property 1 required
PayorDetailedResponse
object
21 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

forta-health-payor-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 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.