# Voter ID API

> Verify a Voter ID in real time. Endpoint: `POST https://api-b2b.stampmitra.in/v1/verify/voter-id`.

Price: ₹5 per successful call, pay-as-you-go (lower on Growth and Scale). Sandbox keys are free. Prices exclude 18% GST.

- HTML docs: https://developer.stampmitra.in/docs/verification/voter-id
- Product page: https://developer.stampmitra.in/products/voter-id
- Pricing: https://developer.stampmitra.in/pricing
- Authentication: https://developer.stampmitra.in/docs/auth

## Verify Voter ID

`POST https://api-b2b.stampmitra.in/v1/verify/voter-id`

Required scope: `verification.voter.read`

Validates and verifies a Voter ID. Requires the `verification.voter.read` scope on the API key. Metered as `voter.verify` after a successful response - usage is only recorded (and the fulfilment wallet debited, for priced services) once verification completes successfully. The response below is the exact real shape returned by `/v1/verify/voter-id`, including its `referenceId` field.

### Parameters

- `Authorization` (header, required): Bearer <api-key> (e.g. sk_test_... in sandbox, sk_live_... in production). The x-api-key header is also accepted.
- `voterId` (string, required): EPIC / Voter ID number.
- `name` (string, optional): Name to match against records.

### Request example

```json
{
  "voterId": "ABC1234567",
  "name": "Rahul Kumar"
}
```

### Response example

```json
{
  "referenceId": "SMV-20260927-7H83M1",
  "valid": true,
  "name": "RAHUL KUMAR",
  "dob": "1990-01-01",
  "gender": "M",
  "age": 35,
  "address": "123, MG Road, Bengaluru",
  "state": "Karnataka"
}
```

### Errors

- 401: Missing or invalid API key
- 403: Valid key, missing required scope
- 400: Validation error
- 402: Insufficient wallet balance
- 429: Rate limited
- 502: Upstream verification service unreachable

Notes: Input format is validated up front - a malformed pan/gstin/etc. fails fast with a 400 rather than being submitted for verification. referenceId (format SMV-YYYYMMDD-XXXXXXX) is StampMitra's own transaction id for this call and is always present, including on a negative (valid: false / found: false) result - both positive and negative determinations are completed, billable verifications. This is not an idempotency key.