Recruitment & HR
Stop mistyped ID numbers from reaching payroll, contracts, and access cards. CheckID checks structure and checksum in under a second, then you continue with the screening your role actually requires.
A transposed digit in a new-hire file can stall SARS submissions, medical-aid capture, and first-pay runs. Structural validation flags impossible dates and failed checksums before HR operations spend hours chasing the candidate.
Recruiters paste IDs from CVs, WhatsApp, and application forms. Invalid numbers create duplicate people records that never merge cleanly with your HRIS.
Sending an invalid ID to a background-check or qualification vendor wastes budget. Filter format failures first, then pay for deeper checks only on structurally valid numbers.
Use the web checker for one-off offer packs. Connect the API when applications should fail fast inside the ATS.
Call the REST endpoint when a candidate submits an application. If the number fails checksum or date rules, ask them to correct it before creating the employee file.
Start with the South African ID validation API. API Starter covers single production calls; bulk ATS imports need Professional.
Agencies and high-volume TA teams often receive CSV lists from job boards. Professional includes bulk API and web bulk validation so you can clean a list before it hits screening vendors.
See Bulk ID validation for recruitment teams and Bulk South African ID validation. R99 API Starter does not include bulk.
An application form often only needs to know whether the ID number is structurally valid before you store a people record. Prefer validating at the point of capture over emailing ID-book scans to a shared inbox.
CheckID does not keep the candidate number. If you retain IDs for payroll, SARS, or employment equity reporting, that is your lawful-purpose and retention decision. Read POPIA and ID number handling.
Validate IDs on offer acceptance so payroll, medical aid, and access-card forms start with a number that can actually pass checksum rules.
Clean inbound CV lists before submitting candidates to clients. Professional bulk keeps agency volume off one-by-one web checks.
Assessment-centre days produce hundreds of forms. Reject invalid IDs at registration instead of discovering them when contracts go out.
After a candidate submits a 13-digit ID, your ATS can call the single-ID endpoint, then create the application only if isValid is true.
# ATS webhook after a candidate submits an ID number
curl -s "https://api.checkid.co.za/api/v1/validate/8001015009087" \
-H "Authorization: Bearer YOUR_API_KEY"8001015009087 is the public sample ID used across CheckID docs — not a live customer number. Replace YOUR_API_KEY with a key from your dashboard. See the South African ID validation API and 5-minute South African ID validation API tutorial.
Free checker for offer-pack spot checks. API Starter from R99/month for live ATS calls. Professional for bulk lists and team seats. Compare the full grid on CheckID pricing for API and bulk plans.
Descriptive links to the checker, API, bulk workflows, and POPIA notes — not a cloned trust grid.
No. CheckID validates the structure of a South African ID number and decodes date of birth, age, gender, and citizenship indicator. It does not query Home Affairs and does not replace background checks, qualification checks, or right-to-work reviews.
Yes, on Professional. API Starter (R99/month) is for up to 1,000 single production calls. Spreadsheet and bulk API imports are a Professional (or Business) workflow, not part of API Starter.
No. ID numbers are processed in memory and discarded after the response is returned. What you keep in your ATS, HRIS, or payroll file remains your organisation’s POPIA responsibility.
Yes. Call the REST API when a candidate submits an application, then block or flag invalid numbers before the record is created. See the South African ID validation API developer guide.
Check one number free, then automate the same structural check in your ATS.