What data fields does a mexico citizen data api return?

A typical mexico citizen data api returns full legal name, date of birth, gender, state of birth, nationality, and CURP number. Some providers also return registered address, marital status, and document validity dates depending on the data source accessed.

Do I need user consent to query a mexico citizen data api?

Yes, under Mexico's LFPDPPP (Federal Law on Protection of Personal Data), you must obtain explicit informed consent from the individual before querying their personal data through any api. This consent must specify what data will be collected and how it will be used.

Looking for a mexico citizen data api — what fields can I actually get back?

luis_dataeng opened this thread · May 12, 2026 · 1 reply

mexico-citizen-data-api RENAPO personal-data KYC

Question

luis_dataeng Asker May 12, 2026

I'm researching options for a mexico citizen data api and I'm confused about what data is actually available programmatically versus what requires manual processes. Our use case is KYC verification for a digital wallet product.

Specifically, I want to understand:

Given a CURP, what personal data fields can a mexico citizen data api return?
Is there a way to do a reverse lookup (name + DOB to find CURP)?
Can I verify that the person's name matches their CURP without getting all their data?
What about deceased person checks — can the API tell me if someone has been reported as dead?

I've read that RENAPO has strict access controls and not every provider can actually query the full dataset. Some apparently only validate the CURP format algorithmically without actually checking the government database. That's insufficient for our compliance requirements.

We need a genuine mexico citizen data api that does live queries against authoritative sources, not just format validation or cached data. Our compliance team requires proof that the data is sourced from official government registries.

What's the realistic scope of data you can get from these APIs? And what are the legal constraints we need to be aware of under LFPDPPP?

Answers

sofia_compliance_mx May 13, 2026

Great questions. I've been working in Mexican identity verification for four years, so let me break down what's actually possible with a mexico citizen data api:

What you can get from RENAPO-connected APIs:

Full legal name (first name, paternal surname, maternal surname)
Date of birth
Gender
State of birth (entidad federativa)
Nationality
CURP validation status (valid, invalid, or deregistered)
Document of origin (birth certificate number)

What you typically cannot get:

Current address (not in RENAPO, would need INE data)
Phone number or email
Photo/biometric data (restricted access tier)
Family relationships

Regarding reverse lookup: Yes, some mexico citizen data api providers support lookup by name + date of birth + state of birth. However, this can return multiple results for common names, so it's not always deterministic. Most compliance frameworks prefer the CURP-first approach.

Deceased person checks: RENAPO does maintain death records, and quality providers flag CURPs associated with deceased individuals. This is critical for fraud prevention and most legitimate providers include this check.

Legal requirements under LFPDPPP:

You must have a published privacy notice (aviso de privacidad)
Explicit consent must be captured before querying personal data
You must specify the purpose (finalidad) for collecting the data
Data retention periods must be defined and enforced
The individual has rights to access, rectify, cancel, and oppose (ARCO rights)

For provider comparison, I'd recommend checking API Pull's marketplace. They list several mexico citizen data api providers with details about which government sources each one connects to. The providers that have genuine RENAPO connections will explicitly state this in their documentation.

● Thread open · 1 reply

Question

Answers

Find API Providers on apipull.com