Certifyos · Schema
FacilityCertificateUpdateRequest
Facility certificate data for PUT operations that replace the entire certifications array
CompanyHealthcareProvider DataCredentialingLicensingPayer EnrollmentPrimary Source VerificationProvider Network ManagementRoster ManagementCompliance MonitoringHealthcare APIWebhook
Properties
| Name | Type | Description |
|---|---|---|
| certificateId | string | The certificate ID |
| certificateType | string | The type of certificate |
| durationType | string | The duration type |
| expirationDate | string | The expiration date of the certificate |
| issueDate | string | The issue date of the certificate |
| speciality | string | The specialty associated with the certificate |
| subspeciality | string | The subspecialty associated with the certificate |
| moc | string | Maintenance of Certification status |
| status | string | The status of the certificate |
| occurrenceType | string | The occurrence type |
| recordType | string | The record type |
| number | string | The certificate number |
| source | string | The source of the certificate |
| createdAt | string | The date the record was created |
| createdBy | string | The user who created the record |
| updatedAt | string | The date the record was last updated |
| updatedBy | string | The user who last updated the record |
| attachments | array | Supporting documents for the certificate |
| verifiedDate | string | The date the certificate was verified |
| verifiedBy | string | The user who verified the certificate |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/certifyos/main/json-schema/certifyos-facility-certificate-update-request-schema.json",
"title": "FacilityCertificateUpdateRequest",
"description": "Facility certificate data for PUT operations that replace the entire certifications array",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/certifyos-facilitycredentialingworkflow-api-openapi.yml#/components/schemas/FacilityCertificateUpdateRequest",
"type": "object",
"required": [
"certificateType",
"number",
"source"
],
"properties": {
"certificateId": {
"type": "string",
"description": "The certificate ID"
},
"certificateType": {
"type": "string",
"pattern": "\\S",
"description": "The type of certificate"
},
"durationType": {
"type": "string",
"description": "The duration type"
},
"expirationDate": {
"type": "string",
"description": "The expiration date of the certificate"
},
"issueDate": {
"type": "string",
"description": "The issue date of the certificate"
},
"speciality": {
"type": "string",
"description": "The specialty associated with the certificate"
},
"subspeciality": {
"type": "string",
"description": "The subspecialty associated with the certificate"
},
"moc": {
"type": "string",
"description": "Maintenance of Certification status"
},
"status": {
"type": "string",
"description": "The status of the certificate"
},
"occurrenceType": {
"type": "string",
"description": "The occurrence type"
},
"recordType": {
"type": "string",
"description": "The record type"
},
"number": {
"type": "string",
"pattern": "\\S",
"description": "The certificate number"
},
"source": {
"type": "string",
"pattern": "\\S",
"description": "The source of the certificate"
},
"createdAt": {
"type": "string",
"description": "The date the record was created"
},
"createdBy": {
"type": "string",
"description": "The user who created the record"
},
"updatedAt": {
"type": "string",
"description": "The date the record was last updated"
},
"updatedBy": {
"type": "string",
"description": "The user who last updated the record"
},
"attachments": {
"type": "array",
"items": {
"$ref": "#/$defs/FacilityCredentialingWorkflowAttachment"
},
"description": "Supporting documents for the certificate"
},
"verifiedDate": {
"type": "string",
"description": "The date the certificate was verified"
},
"verifiedBy": {
"type": "string",
"description": "The user who verified the certificate"
}
},
"$defs": {
"FacilityCredentialingWorkflowAttachment": {
"type": "object",
"required": [
"fileType",
"fileUrl",
"originalFileName"
],
"description": "Attachment metadata for facility credentialing workflow sections",
"properties": {
"createdAt": {
"type": "string",
"description": "The date the attachment was created"
},
"fileType": {
"type": "string",
"description": "Supporting Document File Type (i.e. Malpractice Insurance Policy, License, etc.)"
},
"fileUrl": {
"type": "string",
"description": "Supporting Document File URI in GCS"
},
"originalFileName": {
"type": "string",
"description": "Supporting Document Original File Name"
},
"state": {
"type": "string",
"description": "The state associated with the supporting document"
},
"expirationDate": {
"type": "string",
"description": "The expiration date of the supporting document"
},
"source": {
"type": "string",
"description": "The source of the supporting document"
},
"createdBy": {
"type": "string",
"description": "The user who created the record"
},
"updatedAt": {
"type": "string",
"description": "The date the attachment was last updated"
},
"updatedBy": {
"type": "string",
"description": "The user who last updated the record"
}
}
}
}
}
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-facility-certificate-update-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.