API & Integrations
iCura's API and webhook layer let technical teams extend the platform and connect it to existing systems. This page is an overview for teams evaluating integration work — see Developers to request early access.
Design principles
The API follows the same rules as the rest of the platform:
- Governed by default. Every API request is scoped to the permissions of the authenticated user or service account making it — there is no separate, less-restricted path into the data.
- Event-driven. Rather than requiring constant polling, iCura emits webhook events for operational changes — a new referral, a completed shift, a compliance flag — so integrations can react in near real time.
- Additive, not required. Every product works fully without any integration work. The API exists to connect iCura to systems you already run, not as a precondition for using the platform.
Common integration patterns
Typical early integrations fall into a few categories, covered in more detail on the Integrations page:
- Payroll and HR systems — syncing timesheets, mileage and training records.
- Finance and accounting platforms — pushing invoicing and cost data.
- Local authority and funder portals — reducing duplicate data entry for commissioned care.
- Communication tools — routing notifications to the channels your teams already use.
Marketplace
Certified integrations and workflow templates are being published to the iCura Marketplace as they're validated with early partners, so common integration patterns don't need to be rebuilt from scratch by every customer.
Requesting access
The API is being made available to technical teams ahead of general availability. Get in touch if you'd like early access or want to discuss a specific integration before committing.