Workforce compliance.
Part of your working day.
Check before the offer. Keep your roster informed. Bring the Career Passport into the tools your team already uses.
API and webhooks today; direct integrations built on demand.
Available with Pro and Enterprise.
One worker-owned record.
A current picture for your team.
The systems your team knows.
From recruitment to the next shift. Bring us your systems and we’ll work through the connection with you.
Recruitment
Greenhouse
Bullhorn
Workable
JobAdder
PageUp
Humanforce Talent
Scout Talent
Lever
HR
Workday
SAP SuccessFactors
Employment Hero
Rippling
HiBob
BambooHR
Rostering
Deputy
Humanforce
Tanda
Skedulo
Team notifications
Slack
Microsoft Teams
Automation
Zapier
Make
These are systems to discuss with us. Named vendors are examples, not shipped connectors or Koora partners. Setup depends on each vendor’s access and permissions.
Check before
the offer.
Bring worker records into Koora and read back role requirements, gaps and current status. Your team can see what needs attention before making the offer.
The worker owns their Career Passport. Your recruitment workflow uses the access and fields agreed during setup.
Explore the workforce API
Worker leaves.
Tracking ends.
Your HR system stays the source of truth for employment. Send starter events to invite workers into Koora, and leaver events to end access after the grace period you choose.
The worker keeps their Career Passport when they leave. Repeated events do not create a second worker.
Status changes.
Your roster responds.
Send status and expiry events to your rostering system. Where your roster supports it, configure rules to alert your team or cancel a shift when a status changes.
Your team configures the actions in your rostering system and keeps legal responsibility for who they engage.
The right update.
In your team's channel.
Route selected events to Slack, Microsoft Teams or your own notification tools. Choose the destination and the people who take the next step.
Document review outcomes are included when Crew is attached. Each destination needs a configured webhook or automation with the right permissions.
Your configured channel
A faster start, with AI.
AI matches your CSV columns and roles. Add proof documents, and it reads the credential details and issue and expiry dates. Our compliance engine then checks those records against each role’s requirements and shows the gaps.
Both audits are free. Worker tracking charges start when you confirm your import. First 5 workers free.
AI processing for both audits runs in Australia. Your audit data is not used to train AI models.
Free CSV audit
AI matches columns and roles. The compliance engine checks the supplied records for gaps. No account needed.
Free full audit
Sign up free and upload proof documents. AI reads the details and dates; the compliance engine checks the evidence against role requirements.
Track when you’re ready
Review the audit and tracking costs, then confirm your import to start tracking.
Start with the workflow.
We'll help with the wiring.
API, webhooks and scheduled file delivery are available with Pro and Enterprise. Choose a route below, or talk it through with Koora's technical support.
Workforce API: records, requirements and status
Add up to 100 workers per call, attach the files you hold, read role requirements from the compliance engine and bring current status back into your tools. Adds are idempotent, so sending the same worker again returns the original.
REST over HTTPS, bearer-key authentication and JSON. Your team or integration partner maps the fields and configures the calls.
POST /v1/workers/bulk
{
"defaults": { "provider_name": "Sunrise Aged Care" },
"workers": [
{
"email": "amara.okafor@example.com",
"first_name": "Amara",
"last_name": "Okafor",
"date_of_birth": "1988-03-14",
"tracked_role_codes": ["direct_care"],
"external_id": "EMP-10482"
},
{
"email": "yonas.tesfaye@example.com",
"first_name": "Yonas",
"last_name": "Tesfaye",
"date_of_birth": "1992-11-02",
"tracked_role_codes": ["registered_nurse"],
"external_id": "EMP-10515"
}
]
}Webhooks: starters, leavers and status changes
Receive starter and leaver events from your HR system. Send selected events out: worker status, credential events, worker records and records you supplied. Document review outcomes require Crew.
Outbound deliveries are signed and retried for twelve hours. Use plain JSON or built-in formats for Slack, Microsoft Teams, Zapier, Make and n8n. A receiving webhook or automation must be configured with permission to take the chosen action.
During setup, agree the events, worker fields and access settings your vendor supports. Test the route and use delivery diagnostics to check the result.
Scheduled workforce files: repeat the export
Your system or an automation sends the CSV to Koora's scheduled file endpoint. Each delivery appears in pending files, with saved column matching carried forward.
Your team reviews and submits each import. Scheduled delivery never changes workforce records unattended. Koora support helps confirm whether your system can deliver the export directly or needs an automation service.
Setup, security and the developer reference
Confirm your vendor's API or export access, subscription requirements and permissions first. Direct integrations are built on demand; Koora provides technical support through mapping, testing and diagnostics.
Keys are scoped to your organisation, or a single service with no organisation above it. Keys are shown once and stored as hashes: keep yours in a secrets manager. Optional IP allowlists reject requests outside the named addresses, including when the source cannot be checked.
Rotate keys with an overlap while your systems move across, or revoke a key immediately. Find every endpoint, field, limit, error code and event payload inside Koora under Settings, then Integrations, beside your keys and endpoint URLs.
Compare Pro and EnterpriseA setup brief for your AI assistant
Hand the wiring to your own AI assistant
Choose the right connection with your team’s AI assistant. File imports wait for review; configured starter and leaver events run automatically. Keep API keys and signing secrets out of the chat.
You are helping me connect my HR system to Koora (koora.care), the care-sector workforce compliance platform. I want my roster to flow into Koora so starters, leavers and credential details stay in step, using reviewed file imports or configured employee events.
Koora offers two inbound channels. Both require a Bearer API key created in Koora under Integrations. Event webhooks also require a timestamp and HMAC signature. The exact URLs and payload reference are shown beside the key:
1. Scheduled file drop (works with any HR system that can schedule a report):
POST the roster export to the "scheduled file drop" URL as JSON:
{ "file_name": "roster.csv", "csv": "<the export's contents>" }
Koora's AI matches the columns, I confirm the matching once, and every
later file re-applies it automatically. Each file waits for my team to
review and submit the import in Koora.
2. Event webhook (for systems that can call an API on employee events):
POST worker.added / worker.removed events to the webhook URL with the
Bearer API key and a timestamped HMAC-SHA256 signature using the webhook
secret. Follow the in-app reference for headers and exact payloads.
Valid events run the configured starter/leaver workflow without a
per-event review screen. Confirm permissions and the leaver grace period
before enabling this route; test with authorised records first.
My HR system is: [NAME YOUR SYSTEM]
Please:
- Tell me whether my system can schedule a report delivery to a URL, emit
employee webhooks, or needs a small automation bridge (Zapier, Make or
Power Automate) in between.
- Give me the exact configuration steps for my system, and build the bridge
automation if one is needed. Keep keys and signing secrets in the
automation platform's secret store; never paste secrets into this chat.
- Use channel 1 unless my system genuinely supports employee event webhooks.
- Do not invent Koora URLs or payload fields: I will paste the real ones
from the Koora Integrations screen when you ask for them.A few things worth knowing.
Does importing a credential make it verified by Koora?
Do we need developers to connect our HR system?
What happens to the records we supplied once a worker claims theirs?
What if our HR system sends the same event twice?
Which task would you connect first?
Tell us the systems you run and the workflow you need. We'll work through the data, permissions and setup with you.