ATS & VMS integrations
Connect Credentialing Check to the system that already runs your staffing workflow. New hires flow in by API or CSV; compliance status flows back out through a signed webhook or an on-demand endpoint — so the record in your ATS matches the record on your desk.
How the integration works
Data moves both directions. Your ATS or VMS sends clinicians to us; we send compliance status back. No per-vendor setup, no waiting on a connector — the module is live today.
The endpoints
Plain REST with a bearer key and JSON. If your system can make an HTTP request, it can talk to us.
Send clinicians in
POST https://credentialingcheck.com/api/public/v1/clinicians
Authorization: Bearer <API key>
Content-Type: application/json
{ "clinicians": [{
"external_id": "BH-10293",
"first_name": "Ana", "last_name": "Lopez",
"email": "ana@example.com",
"profession": "RN", "specialty": "ICU",
"state": "FL", "license_number": "RN9384"
}] }Read compliance status anytime
GET https://credentialingcheck.com/api/public/v1/clinicians
Authorization: Bearer <API key>
{ "clinicians": [{
"external_id": "BH-10293",
"compliance": "expiring_soon",
"expired_count": 0, "expiring_count": 1,
"credentials": [{ "type": "RN License",
"status": "expiring_soon",
"expiration_date": "2026-10-22" }] }] }Signed webhook push
Save your webhook URL once and press Send status now to push a snapshot. Every delivery is signed with HMAC-SHA256 over a timestamp plus the payload, so your system can verify it came from us.
Key security built in
Keys are per-agency and stored hashed — shown once at creation, then only a short prefix. Rotate any time; the old key stops working immediately.
Inside your dashboard
The integration lives in your agency workspace — not in a separate portal. Everything runs through the Integrations page and the ATS/VMS sync panel on your dashboard.
Create a key and save your webhook
On the Integrations page of your dashboard, create a secret API key (shown once — only a short prefix is stored) and paste in the webhook URL of your ATS or VMS. We issue a signing secret for the webhook at the same time.
Clinicians flow in
Your system pushes new hires by API, or your team drops in a CSV export and maps the columns. Imported clinicians land in your roster like any other clinician — with the same checklists, reminders and compliance scoring.
Status flows back out
Your system reads status on demand with the GET endpoint, or you press Send status now to push a signed snapshot to your webhook: each clinician's compliance level, expired and expiring counts, and every credential with its status and expiration date.
You see everything in the activity log
The Integrations page and the ATS/VMS sync panel on your dashboard show the last time data was received and sent, and every recent import and send marked as worked or failed — so you always know the pipeline is alive.
Straight answers
It works with any system that can send or receive web requests — which covers most of them, directly or through automation tools like Zapier or Make. There are no per-vendor approvals: your agency's own secret key is the credential.
Each clinician's compliance level (current, expiring soon, or expired), how many credentials are expired or expiring, and each tracked credential with its type, status and expiration date. Documents and files never leave Credentialing Check — your system gets status, not paperwork.
Every key is per-agency and stored hashed — the full key is shown once at creation, then only a short prefix. Webhook deliveries are signed with HMAC-SHA256 over a timestamp plus the payload, so your system can verify they came from us. Only agency owners and admins can manage integrations.
Not yet. Status goes out when someone on your team presses Send status now, or your system can pull status on demand with the GET endpoint. Scheduled automatic pushes are on the roadmap.
The integration module is included on paid plans (Starter, Pro and Agency) and is a core part of the Enterprise Integrated tier, which adds scoped direct connection work and priority on the public API roadmap. Free accounts see the module but can't use it until they upgrade.
We moved off a shared spreadsheet and never looked back. Expiration reminders go out on their own now — I stopped worrying about a lapse slipping through.
Our hospitals ask for credential status constantly. The client portal lets them see exactly what they need without me emailing PDFs all day.
Setup took less than an afternoon. We imported our roster, uploaded the licenses we had on file, and the compliance scores were live the same day.
The integration module is included on every paid plan. For direct connection work, custom data flows and priority on the public API roadmap, the Enterprise Integrated tier is the fit.
Want the full setup walkthrough? Connect your VMS step by step.
Already on a paid plan? Create your API key and import clinicians right now on the Integrations page of your dashboard — signed in, under Integrations in the sidebar.