South African product teams often need an SA ID validator API inside onboarding forms, payroll imports, or partner integrations. CheckID exposes a REST endpoint that returns predictable JSON for each 13-digit number: validity, encoded date of birth, age, gender, and citizenship indicator where derivable from the digits.
The API performs the same structural rules as the public web validator. Processing happens in memory over TLS; CheckID does not store raw ID numbers or decoded validation payloads on our servers.
What a single validation request looks like
Authenticate with a bearer token from your account. For a single ID, call GET /api/v1/validate/8001015009087 (replace the path segment with the number under test). A successful response includes isValid, dob, age, gender, and citizenship fields using the names documented in the developer guide.
When an API beats the web tool
An API gives you real-time feedback right inside your own internal software, eliminating the need to visit checkid.co.za to do your ID checks.
For higher throughput, pair this guide with bulk SA ID validation when files arrive with dozens or hundreds of rows.
Operational hygiene for API keys
Rotate bearer tokens from your dashboard, scope keys per environment, and avoid logging full request bodies where ID numbers could leak into application logs or error trackers. CheckID's zero-storage design on our side complements — but does not replace — your own data-minimisation policies.
Clear boundaries for product and compliance teams
An SA ID validator API is a hygiene layer: it catches typos, impossible dates, and checksum failures early. It is not a substitute for document verification, biometric matching, or Home Affairs database lookups. Position it accurately in privacy notices and sales material.
Read how SA ID numbers are structured to share context with non-technical stakeholders, then compare plans on pricing when you are ready to move from the homepage tool to production API access.