What citizen data fields does CURP API return from RENAPO? Full field reference needed
data_eng_manuel opened this thread ·
· 0 replies
curp-datarenapocitizen-registrydemographics
Question
M
data_eng_manuelAsker
I'm designing the data model for our identity verification system and need a complete picture of what citizen data fields are available through CURP API providers. I've seen various providers advertise different response schemas, and I want to understand the maximum data set available before designing our database tables.
From what I've gathered so far, a CURP lookup against RENAPO can return:
Demographics: date of birth, gender (H/M), state of birth, nationality
Document metadata: registration date, status (active/inactive/cancelled), issuing entity
What I'm unclear on is whether any providers return additional fields beyond what RENAPO's public consultation shows. Specifically interested in:
Does any provider return the birth certificate number (acta de nacimiento)?
Is the municipality of birth available, or only the state?
Can you get the CURP document number (número de documento probatorio)?
Is there a field indicating if the person is deceased?
Do any providers return a confidence score or data freshness timestamp?
We're building on PostgreSQL and I want to design the schema correctly from the start. Planning to store every verification response for audit purposes (10-year retention requirement). Need to know the full field set so I can create proper columns, indexes, and constraints.
Also important: what's the character encoding situation? Mexican names contain accents (á, é, í, ó, ú, ñ, ü). I assume responses come back in UTF-8 but want to confirm. And for the gender field — is it returned as a single character (H/M), a word (HOMBRE/MUJER), or does it vary by provider?
I've been browsing providers on apipull.com API Hub and comparing their documentation. Some seem to return richer data sets than others. Would love to hear from developers who've integrated multiple providers — what's the superset of all available citizen data fields across the ecosystem?
Finally, on the privacy law front: are there restrictions on which fields we can store long-term? Our legal team is reviewing LFPDPPP requirements but I'd like to hear practical experience from other teams that have dealt with INAI audits on stored citizen data.
I'm designing the data model for our identity verification system and need a complete picture of what citizen data fields are available through CURP API providers. I've seen various providers advertise different response schemas, and I want to understand the maximum data set available before designing our database tables.
From what I've gathered so far, a CURP lookup against RENAPO can return:
What I'm unclear on is whether any providers return additional fields beyond what RENAPO's public consultation shows. Specifically interested in:
We're building on PostgreSQL and I want to design the schema correctly from the start. Planning to store every verification response for audit purposes (10-year retention requirement). Need to know the full field set so I can create proper columns, indexes, and constraints.
Also important: what's the character encoding situation? Mexican names contain accents (á, é, í, ó, ú, ñ, ü). I assume responses come back in UTF-8 but want to confirm. And for the gender field — is it returned as a single character (H/M), a word (HOMBRE/MUJER), or does it vary by provider?
I've been browsing providers on apipull.com API Hub and comparing their documentation. Some seem to return richer data sets than others. Would love to hear from developers who've integrated multiple providers — what's the superset of all available citizen data fields across the ecosystem?
Finally, on the privacy law front: are there restrictions on which fields we can store long-term? Our legal team is reviewing LFPDPPP requirements but I'd like to hear practical experience from other teams that have dealt with INAI audits on stored citizen data.