Application APIs
Beyond FHIR, OvokClient exposes typed helpers for application workflows. The project must be configured for each backend capability, and authenticated calls are still subject to project access policy.
| Domain | SDK surface | Ovok documentation |
|---|---|---|
| CMS and published content | CMS document reads, legal pages, release notes, translations | CMS |
| Email template catalog | getEmailTemplates(), useEmailTemplates() | Email templates |
| Video calls | Appointment creation, access, and appointment listing | Video calls |
| Consent and documents | Consent signatures and document upload/download helpers | FHIR and primitives |
| Invitations and sharing | Patient/practitioner invites and patient sharing | Invitations |
| AI and translation | AI chat, AI FHIR search, text translation | Working with AI agents |
| Bots | Execute a bot through the supported SDK method | Ovok primitives |
Read the linked backend guide before designing a flow. It explains prerequisites, feature flags, project settings, route behavior, and server-side authorization that the SDK types cannot express on their own.
Billing is not part of the current @ovok/core contract. Do not build billing flows against guessed methods or routes.