Runs alongside the systems you already have.
Read API, webhooks and SSO now. Deeper EHR, CMMS and HRIS links come later.
In short
IncidentKit has a read API for incidents and signed webhooks for incident events (created, submitted, status changed, closed). It also offers SSO and email intake. It runs alongside your EHR, CMMS and HRIS, not in place of them. Deeper connections are rolling out.
SAMPLE RECORD · SYNTHETIC DATA
Integrations and API
Read API
List and fetch incidents with organization-scoped keys. Sensitive fields need a separate scope.
Signed webhooks
Events for created, submitted, status changed and closed. Each is signed with HMAC and retried on failure.
SSO
Single sign-on per organization.
Email in
Create incidents by email.
EHR, CMMS, HRIS connectors
Pre-built links to health record (EHR), maintenance (CMMS) and HR (HRIS) systems, including PointClickCare and MatrixCare, are rolling out.
Rolling outWrite API
Creating and updating incidents through the API is on the roadmap.
Rolling out
From first touch to done.
- Create an API keyScoped to your organization.
- Subscribe to eventsPoint a webhook at your system.
- Build the workflowPage a team, open a work order, update a dashboard.
Integrations and API: frequently asked
Something we missed? Ask us, and a person answers.
Do you replace our EHR or CMMS?
No. IncidentKit runs alongside them. Staff report from a phone without opening a chart or work order, and the API and webhooks let other systems react to incidents.
Are webhooks secure?
Yes. Payloads are signed so your receiver can check they came from IncidentKit, and failed deliveries are retried.
Is there an API for writing incidents?
No. The API is read-only today, and a write API is on the roadmap.
Start with one incident.
Create your kit in about ten minutes and report the first incident the same day. Free to start, no card.