Verifies a Mexican INE / IFE voter ID credential against the INE registry (modelo, vigencia, válida-como-identificación, derecho-a-votar). Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results. ## Coverage * **Coverage:** — * **Country:** Mexico * **Service ID:** `mex_ine_vigencia` * **Data domain:** Identity * **Category:** NationalIDRegistry ## Inputs | Field | Required | Example | | ------------------------- | -------: | --------------- | | `cic` | No | `123456789` | | `identificador_ciudadano` | No | `123456789` | | `ocr` | No | `1234567890123` | | `voter_number` | No | `ABCDEF123456` | | `emission_number` | No | `01` | | `first_name` | No | `John` | | `last_name` | No | `Doe` | | `date_of_birth` | No | `1990-01-01` | | `vendor_data` | No | `user-1234` | * **Required inputs:** — * **Optional inputs:** `cic`, `identificador_ciudadano`, `ocr`, `voter_number`, `emission_number`, `first_name`, `last_name`, `date_of_birth`, `vendor_data` * **Consent:** Not required * **Workflow availability:** Available in workflow * **Coverage:** — * **Price:** \$0.20 per successful query ## Body parameters ISO 3166-1 alpha-3 country code for this database service. Example: `MEX` Array containing this service ID. Pinning the service keeps the request scoped to this exact database. Example: `mex_ine_vigencia` `cic` value required by this database service. Example: `123456789` `identificador_ciudadano` value required by this database service. Example: `123456789` `ocr` value required by this database service. Example: `1234567890123` `voter_number` value required by this database service. Example: `ABCDEF123456` `emission_number` value required by this database service. Example: `01` Given name to validate. Example: `John` Family name to validate. Example: `Doe` Date of birth in `YYYY-MM-DD` format. Example: `1990-01-01` Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise. Example: `user-1234` ## Input rules & validation notes * Send the fields listed above exactly as captured from the user or document. * Didit validates required fields before calling the database. Requests rejected before source lookup are not charged. ## How to call it ```bash cURL theme={null} curl -X POST "https://verification.didit.me/v3/database-validation/" \ -H "x-api-key: YOUR_API_KEY" \ -F "issuing_state=MEX" \ -F "services=mex_ine_vigencia" \ -F "vendor_data=user-1234" ``` Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it. **`MATCH`** — The registry confirmed the identity and every checked field matched. ```json 200 OK — MATCH theme={null} { "request_id": "req_01H…", "status": "Approved", "issuing_state": "MEX", "match_type": "full_match", "validations": [ { "outcome_code": "MATCH", "service_id": "mex_ine_vigencia", "service_name": "Mexico - INE credential validity verification", "source_data": { "emission_number": "SAMPLE-12345", "emission_year": "sample_value", "expiration_date": "1990-01-01", "federal_district": "sample_value", "identification_number": "SAMPLE-ID-12345", "message": "sample_value", "message_code": "sample_value", "ocr": "sample_value", "registration_year": "sample_value", "validation_code": "SAMPLE-12345", "voter_number": "SAMPLE-12345" }, "validation": { "identification_number": "full_match" } } ] } ``` **`NO_MATCH`** — The registry returned no match for the submitted data. ```json 200 OK — NO_MATCH theme={null} { "request_id": "req_01H…", "status": "Declined", "issuing_state": "MEX", "match_type": "no_match", "validations": [ { "outcome_code": "NO_MATCH", "service_id": "mex_ine_vigencia", "service_name": "Mexico - INE credential validity verification", "source_data": { "identification_number": "NO_MATCH" }, "validation": { "identification_number": "no_match" } } ] } ``` ## Returned data The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `mex_ine_vigencia` currently documents this normalized shape: * `emission_number` * `emission_year` * `expiration_date` * `federal_district` * `identification_number` * `message` * `message_code` * `ocr` * `registration_year` * `validation_code` * `voter_number` ## Pricing & SLAs Mexico - INE credential validity verification queries are billed only when Didit receives a conclusive result from the validation source. * **Per-call price:** \$0.20 USD. * **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source. * **Latency:** typical p95 \< 2 s. * **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset. ## Continue reading * [Mexico Database Validation overview](/api-reference/database-validation/mexico) * [Database Validation overview](/core-technology/database-validation/overview) * [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)