Certifyos · Schema
AssociateFacilityNetworkRequest
Request to associate a facility with one or more networks
CompanyHealthcareProvider DataCredentialingLicensingPayer EnrollmentPrimary Source VerificationProvider Network ManagementRoster ManagementCompliance MonitoringHealthcare APIWebhook
Properties
| Name | Type | Description |
|---|---|---|
| groupId | string | ID of the group that the network belongs to |
| networkId | string | Single network ID (legacy). Mutually exclusive with networkIds. |
| networkIds | array | Bulk network IDs (CP-32346). Mutually exclusive with networkId. |
| includeAllActiveFacilityLocations | boolean | When true, associate all active facility locations under the facility/group |
| facilityLocationIds | array | Certify location IDs to associate (optional when includeAllActiveFacilityLocations is true) |
| networkEffectiveDate | string | Effective date for facility and location network associations |
| groupEffectiveDate | string | Effective date for the TenantGroupFacility relationship |
| networkAssociations | array | Grouped network associations (CP-32346): one entry per network, each with its own effective date. Allows associating multiple networks with different effective dates in a single request. Mutually excl |
| legacySingleNetworkRequest | boolean | |
| groupedNetworkRequest | boolean | |
| bulkNetworkRequest | boolean | |
| networkInputValid | boolean |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/certifyos/main/json-schema/certifyos-associate-facility-network-request-schema.json",
"title": "AssociateFacilityNetworkRequest",
"description": "Request to associate a facility with one or more networks",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/certifyos-facility-api-openapi.yml#/components/schemas/AssociateFacilityNetworkRequest",
"type": "object",
"required": [
"groupId"
],
"properties": {
"groupId": {
"type": "string",
"pattern": "\\S",
"description": "ID of the group that the network belongs to"
},
"networkId": {
"type": "string",
"description": "Single network ID (legacy). Mutually exclusive with networkIds."
},
"networkIds": {
"type": "array",
"items": {
"type": "string"
},
"description": "Bulk network IDs (CP-32346). Mutually exclusive with networkId."
},
"includeAllActiveFacilityLocations": {
"type": "boolean",
"description": "When true, associate all active facility locations under the facility/group"
},
"facilityLocationIds": {
"type": "array",
"items": {
"type": "string"
},
"description": "Certify location IDs to associate (optional when includeAllActiveFacilityLocations is true)"
},
"networkEffectiveDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Effective date for facility and location network associations"
},
"groupEffectiveDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Effective date for the TenantGroupFacility relationship"
},
"networkAssociations": {
"type": "array",
"items": {
"$ref": "#/$defs/NetworkAssociationEntry"
},
"description": "Grouped network associations (CP-32346): one entry per network, each with its own effective date. Allows associating multiple networks with different effective dates in a single request. Mutually exclusive with networkId/networkIds."
},
"legacySingleNetworkRequest": {
"type": "boolean"
},
"groupedNetworkRequest": {
"type": "boolean"
},
"bulkNetworkRequest": {
"type": "boolean"
},
"networkInputValid": {
"type": "boolean"
}
},
"$defs": {
"NetworkAssociationEntry": {
"type": "object",
"required": [
"networkId"
],
"description": "A single network with its own effective date",
"properties": {
"networkId": {
"type": "string",
"pattern": "\\S",
"description": "Network ID for this association"
},
"effectiveDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Effective date applied to this network"
}
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/certifyos-associate-facility-network-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.