Manual Identity Verification
Manual Identity Verification allows you to perform identity checks by providing data via API, which can be extracted from identity documents using OCR (Optical Character Recognition) or other methods. This is useful for scenarios where direct integration with government databases is not feasible or for custom verification workflows.
Endpoint
POST /v1/verify/manual
Request Body
Field | Type | Description | Required |
---|---|---|---|
id_number | string | The South African ID number. | Yes |
first_name | string | The first name of the individual. | Yes |
last_name | string | The last name of the individual. | Yes |
date_of_birth | string | Date of birth in YYYY-MM-DD format. | Yes |
gender | string | Gender of the individual (e.g., "Male", "Female"). | No |
image_url | string | (Optional) URL of the identity document image for reference. | No |
Example Request
POST /v1/verify/manual HTTP/1.1
Host: api.e-verify.co.za
X-API-Key: ev_live_YOUR_API_KEY
Content-Type: application/json
{
"id_number": "8001015009087",
"first_name": "John",
"last_name": "Doe",
"date_of_birth": "1980-01-01",
"gender": "Male",
"image_url": "https://example.com/id_card.jpg"
}
Response
{
"request_id": "req_manual_1234567890",
"status": "completed",
"result": {
"id_number_match": true,
"first_name_match": true,
"last_name_match": true,
"date_of_birth_match": true,
"gender_match": true,
"overall_status": "verified"
},
"message": "Manual identity verification completed successfully."
}
Error Codes
Code | Description |
---|---|
400 | Invalid input data |
401 | Unauthorized |
403 | Forbidden |
500 | Internal server error |