EWS Certificate Verification

This document describes state-wise inputs required to verify EWS certificates via this service, and how to obtain captcha where applicable.

EWS Certificate Structure

Key	Description
EWS Number	Unique EWS/Certificate/Application number
Name	Applicant name (only for specific states)
Security Code	Security code printed on certificate (Kerala)
Captcha	Captcha text solved for the verification
Token	Anti-forgery/request token (Delhi only), found in captcha response

Verification Modes

EWS certificate verification supports two modes:

Automatic Verification (Instant)

The following states support automatic verification with instant results:

State	Code	Requires Name	Requires Captcha	Requires Token	Requires Security Code	Number Format (masked)
Andhra Pradesh	AP	No	No	No	No	CGCXXXXXXXXXXXX (15)
Bihar	BR	Yes	No	No	No	EWSCO/XXXX/XXXXXX (17)
Chhattisgarh	CT	No	No	No	No	XXXXXXXXXXXXXXXX[X] (16–17)
Delhi	DL	Yes	Yes	Yes	No	XXXXXXXXXXXXXX (14)
Haryana	HR	No	No	No	No	HAXXXXXXXXXX (12)
Kerala	KL	No	No	No	Yes	XXXXXXXX (8)
Odisha	OR	No	No	No	No	XXXXXXXX (8)
Punjab	PB	No	No	No	No	ESXXXXXXXX (10)
Rajasthan	RJ	No	No	No	No	XXXXXXXXXXXX (12)
Tamil Nadu	TN	No	Yes	No	No	TN-XXXXXXXXXXXXXX (16)
Telangana	TG	No	No	No	No	CNDXXXXXXXXXXXXXXX (15)

Manual Verification

All other states (not listed above) fall under manual verification mode. For manual verification:

• documentUrl is mandatory - you must provide the document URL/image url for manual processing
• Verification is not instant and requires manual review

Supported states for manual verification:

State	Code
Andaman and Nicobar Islands	AN
Arunachal Pradesh	AR
Assam	AS
Chandigarh	CH
Dadra and Nagar Haveli	DN
Daman and Diu	DD
Goa	GA
Gujarat	GJ
Himachal Pradesh	HP
Jammu and Kashmir	JK
Jharkhand	JH
Karnataka	KA
Lakshadweep	LA
Ladakh	LD
Madhya Pradesh	MP
Maharashtra	MH
Manipur	MN
Meghalaya	ML
Mizoram	MZ
Nagaland	NL
Puducherry	PY
Sikkim	SK
Tripura	TR
Uttar Pradesh	UP
Uttarakhand	UT
West Bengal	WB

API Integration

• Endpoint to get captcha (if required by state):

  • POST /ews-certificate/pre

• Endpoint to verify and fetch certificate details (send captcha answer if required):

  • POST /ews-certificate

Captcha fetch (DL, TN)

Request:

{
  "state": "DL"
}

Response:

{
  "captcha": "<base64 image>",
  "token": "<anti-forgery token if required>"
}

Verify request examples

Automatic Verification Examples

• Delhi (requires name + captcha + token):

{
  "state": "DL",
  "ewsNumber": "XXXXXXXXXXXXXX",
  "name": "JOHN",
  "captcha": "7h2joU",
  "token": "<token-from-captcha-api>"
}

• Bihar (requires name):

{
  "state": "BR",
  "ewsNumber": "EWSCO/XXXX/XXXXXX",
  "name": "JOHN DOE"
}

• Kerala (requires securityCode):

{
  "state": "KL",
  "ewsNumber": "XXXXXXXX",
  "securityCode": "3RMPZ"
}

• Tamil Nadu (requires captcha):

{
  "state": "TN",
  "ewsNumber": "TN-XXXXXXXXXXXXXX",
  "captcha": "A1B2C3"
}

• States with only number (examples: AP, CT, HR, OR, PB, RJ, TG):

{
  "state": "AP",
  "ewsNumber": "CGCXXXXXXXXXXXX"
}

Manual Verification Examples

For states not supporting automatic verification, documentUrl is mandatory.

To generate documentUrl, use File Upload API, where for folderName, use "ews-certificate"

• West Bengal (manual verification):

{
  "state": "WB",
  "ewsNumber": "XXXXXXXXXXXXXXXX",
  "documentUrl": "https://example.com/ews-certificate.pdf"
}

• Maharashtra (manual verification):

{
  "state": "MH",
  "ewsNumber": "XXXXXXXXXXXXXXXX",
  "documentUrl": "https://example.com/ews-certificate.jpg"
}

• Karnataka (manual verification):

{
  "state": "KA",
  "ewsNumber": "XXXXXXXXXXXXXXXX",
  "documentUrl": "https://example.com/ews-certificate.png"
}

Successful Response

Automatic Verification Response

For states with automatic verification, you get instant results:

{
  "code": 0,
  "message": "Success",
  "data": {
    "certificateNumber": "XXXXXX",
    "name": "RXXXX XXXXXA",
    "fatherName": "JUXXXL XXXXR SXXXXA",
    "motherName": "SXXXN XXXI",
    "village": "XXXXXXX",
    "mandal": "XXXXXXXXX",
    "district": "JXXXXXXXXXX",
    "cast": "BXXXXXXX",
    "income": "1XXX",
    "address": "XXXXX  XXXXX XXXx",
    "age": "XX",
    "gramPanchayat": "XXXXXXXXX",
    "pinCode": "XXXXXX",
    "aadharId": "XXXXXXX",
    "mode": "automatic"
  }
}

Manual Verification Response

For states requiring manual verification, the response indicates manual processing:

{
  "code": 0,
  "message": "Success",
  "data": {
    "status": "IN_PROGRESS",
    "mode": "manual",
    "id": "68e5131e3ff7588de909a0bf"
  }
}

id field explanation: For manual verification response is available later via webhook, same id is provided in the webhook.

mode field explanation:

• "automatic": Instant verification was performed and results are immediately available
• "manual": Document has been submitted for manual review and results will be available later

Webhook Response Payload

{
    "id": "68e5131e3ff7588de909a0bf",
    "action": "verification-completed",
    "scope": "automatic-verification",
    "data": {
        "candidate_name": "Candidate Name",
        "given_father_name": "Candidate Father Name",
        "given_certificate_number": "XXXXXX",
        "verified_name": "Candidate Name",
        "verified_father_name": "Candidate Father Name",
        "verified_certificate_number": "XXXXXX",
        "result": "SUCCESS",
        "reason": "VERIFIED",
        "remarks": "The ews certificate has been verified successfully",
        "date_of_completion": "1759234872",
        "pdf_serving_url": "https://example.com/ews-certificate.pdf"
    }
}

Invalid/Not found Response (example)

{
  "code": 0,
  "message": "Success",
  "data": {
    "status": "INVALID",
    "message": "Invalid EWS Certificate"
  }
}