South African product and data teams often need to validate dozens or hundreds of ID numbers after a CSV import, a partner file drop, or a nightly sync. Row-by-row manual checks do not scale; a dedicated bulk ID validation API keeps throughput high and rules consistent.
CheckID exposes a bulk endpoint that accepts multiple South African ID numbers in one request (up to the documented per-request limit), returning structured results for each entry. Processing remains structural: format, embedded fields where derivable from the number, and checksum—without Home Affairs lookups or document authentication.
Use the documented request and response shape
Keep your integration aligned with the canonical docs, the ID Validator API guide and the 5-minute tutorial. For bulk requests, send a JSON object with an idNumbers array in the body, for example { "idNumbers": ["8001015009087"] }.
Response objects use the documented field names: idNumber, isValid, dob, age, gender, and citizenship. The bulk endpoint returns an array of these objects.
What “bulk structural validation” gives you
- Deterministic validation logic shared with the single-ID endpoint.
- Predictable JSON you can map straight into staging tables or exception queues.
- Lower network overhead compared with issuing one HTTP call per row.
You still own downstream decisions: what to store, how long to keep it, and when a failed row should trigger a human review. CheckID's zero-storage design means we are not building a shadow database of your applicants' ID numbers.
Auth, environments, and operational hygiene
API access uses bearer tokens tied to your Professional or Business subscription. Rotate keys from the dashboard, restrict tokens per environment, and avoid logging full request bodies where ID numbers could leak into application logs or error trackers.
For step-by-step wiring, follow the 5-minute integration walkthrough and the canonical reference in the developer guide.
Pair bulk validation with domain-specific UX
Property teams can combine bulk checks with the context in bulk ID verification for property managers. HR teams should read HR recruitment validation at scale for intake policy reminders.
Try the product path that matches your volume
Use the interactive validator while you prototype, then move to the API when you are ready for automation. Read how SA ID numbers are structured if your team needs context on checksum and date encoding rules. Compare quotas and features on pricing before you go live.