Voter ID Verification API
Check the elector details recorded against an EPIC number, and use the result to support a customer's name, age band and stated address inside your own KYC flow.
Overview
Voter ID verification checks the details recorded against an Elector's Photo Identity Card, using the EPIC number printed on it. It is one of the officially valid documents Indian onboarding processes accept, and a practical route for customers who would rather not share another identifier. An API lookup returns the available elector details in a structured response. Your code does the comparison against what the customer told you. Which fields come back depends on the data source and the record. Treat it as a corroborating document. A roll entry shows where a customer was registered, not where they live today, and it carries nothing financial. It supports an identity file alongside other checks instead of replacing them.
- Category
- KYC Services
- Coverage
- Elector roll information available in India. Your service contract sets the coverage.
- Input
- An EPIC number from the card, plus the state where your flow collects one to narrow the search
- Output
- Available elector details, such as name, relation name, age band, constituency and roll address. Fields differ by data source and record.
- Typical users
- Lenders and NBFCs, fintech and payment platforms, insurers, real estate and rental platforms, staffing and gig platforms
- Coverage note
- Corroborating evidence only. A roll entry reflects the registered address, which may not be the current one.
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Endpoint URL and method
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Authentication
Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Request parameters
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused. | 8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$ |
Body
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^[A-Z]{3}[0-9]{7}$ |
input. | string | Optional | OPTIONAL (Release 1.1): a name to compare with the record's; the answer's nameMatchScore is the comparison. | Matches ^(?=.*[A-Za-z])[A-Za-z .'-]+$. 1 to 120 characters |
options | object | Required | Settings for this call. This API requires consent. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Required | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What the check is for, for example kyc. | 1 to 64 characters |
Request samples
cURL
curl -X POST https://gateway.staging.finsour.io/v1/identity/voter-id \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"input": {
"epicNumber": "<epicNumber>"
},
"options": {
"consent": {
"obtained": "<obtained>",
"at": "<at>",
"purpose": "<purpose>"
}
}
}'Node.js
const response = await fetch("https://gateway.staging.finsour.io/v1/identity/voter-id", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"Content-Type": "application/json",
},
body: JSON.stringify({
"input": {
"epicNumber": "<epicNumber>"
},
"options": {
"consent": {
"obtained": "<obtained>",
"at": "<at>",
"purpose": "<purpose>"
}
}
}),
});
console.log(response.status, await response.json());Python
import os
import uuid
import requests
response = requests.post(
"https://gateway.staging.finsour.io/v1/identity/voter-id",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"input": {
"epicNumber": "<epicNumber>",
},
"options": {
"consent": {
"obtained": "<obtained>",
"at": "<at>",
"purpose": "<purpose>",
},
},
},
timeout=30,
)
print(response.status_code, response.json())Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Response schema
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | — | Matches ^[A-Z]{3}[0-9]{7}$ |
data. | string | Sometimes | The voter ID (EPIC) number in its display form — six Xs and the last four digits — from FinSour-Version 2026-11-01 (absent before it). Beside the full epicNumber for one release; the full field is removed in the next version. | Matches ^X{6}[0-9]{4}$ |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | The polling station the roll assigns (Release 1.1). | — |
data. | number or null | Always | How closely nameToMatch matches the name the record holds, 0 to 100, to two decimals; null when no name was sent. | Minimum 0. Maximum 100 |
data. | object | Always | — | — |
data. | string | Always | When the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset. | Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$ |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Error codes
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
CONSENT_REQUIRED | 422 | This product requires an explicit consent flag. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The upstream source did not respond in time. | Safe to retry |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Rate limits
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Use cases
- Lending and NBFC: support an applicant address on a loan file
- Fintech and PSP: offer an alternative document route at onboarding
- Insurance: corroborate proposer name and age band at proposal
- Real estate: support a tenant or buyer address claim before an agreement
- Staffing and gig platforms: corroborate worker identity and locality
- Marketplaces: add a supporting document to a seller identity file
What this service does
A document most customers already hold
Voter ID is one of the officially valid documents Indian onboarding processes accept, and it is widely held. That makes it a workable route for customers whose document set is otherwise thin.
What an elector entry can show
Elector name, relation name, age or year of birth, gender, constituency and part details, polling station, and the address as recorded on the roll. The fields you get depend on the underlying data source and the record.
Your code does the comparing
The available details come back as structured fields. Your flow scores the match against what the customer stated. Nothing rests on how carefully a reviewer read a photograph of a card.
The limits of a roll match
A roll entry confirms a registered address that may no longer be current, and it carries no financial signal. It corroborates an identity file alongside other checks.
How a check runs
Capture the EPIC number and consent
Take the EPIC number in your own form alongside informed consent for the specific purpose, and keep the consent record joined to the lookup that follows.
Send the EPIC number, and the state if you use one
Submit the EPIC number. Adding the state, where your flow collects it, narrows the search before the available elector entry comes back.
Get the elector entry back
Your application receives the details the record holds as structured fields, ready to handle in code instead of retyping them from an image.
Score the entry against what the customer told you
Compare the name, age band and address with the details already on file, at the level your risk process needs. Do not demand a character-for-character address match.
Accept, ask for more, or switch document
Accept the corroboration, request another document where the match is partial, or move to a different officially valid document where no entry is reachable.
Questions
- What is a Voter ID verification API?
- An interface that looks up the elector details recorded against an EPIC number from inside your own application. The details come back as structured fields instead of a photograph of the card for someone to read.
- Can I use a Voter ID as address proof?
- It is one of the officially valid documents Indian onboarding processes accept, and a roll match is real supporting evidence. It confirms the address the elector was registered at, which may not be where they live now. Use it to support a stated address.
- What details come back from an EPIC number lookup?
- Depending on the record, the response can hold the elector name, a relation name, age or year of birth and gender. It can also hold the constituency and part details, the polling station and the roll address. Available fields vary with the data source and the record.
- Can a Voter ID check replace a PAN or bank account check?
- No. An EPIC number cannot support a deduction, payout or account-ownership decision, since there is no tax identifier, bank relationship or credit signal behind it. It corroborates identity and address alongside the checks those decisions rely on.
- What should I do when no elector entry is found?
- Treat it as a routine outcome. Entries can be missing, moved or recorded differently. Route to another officially valid document instead of refusing the application.
- Do I need consent to look up elector details?
- Yes. Elector details are personal data, and a lookup needs informed consent for that specific purpose, with a lawful and authorized business reason. The result must never be used for political profiling or targeting.
Catalog entry last updated .