Mexico CURP Verification

overview and purpose overview the mexico curp verification api is a specialized digital tool designed specifically for businesses operating within mexico this api provides crucial support in confirming the authenticity of personal information against official mexican records, enhancing trust, accuracy, and compliance across various sectors key features and functionalities identity verification the api rigorously checks personal details such as first name, last name, gender, date of birth, and national id number against mexico's national identity databases this is essential for confirming the identity of individuals in processes like account creation, financial transactions, and access to services identity protection by verifying identities against official records, this api plays a vital role in preventing identity theft and fraud it ensures that only authenticated individuals gain access to sensitive services and information business trust for sectors such as banking, finance, and telecommunications, where customer identification is critical, this api builds a foundation of trust by ensuring that all verified information is accurate and reliable compliance support the api helps businesses meet stringent regulatory requirements by providing reliable verification services that comply with mexican laws and guidelines this is particularly crucial in industries like finance and healthcare, where precise identity verification is mandatory the mexico curp verification api not only secures and streamlines customer onboarding and transactions but also reinforces compliance and trust, making it an indispensable tool for businesses aiming to maintain high standards of identity verification within mexico api details api overview the verification api enables the validation of various personal data inputs, including first name, last name, middle name, date of birth, gender, national id number each input is cross referenced against authorized sources to determine a match or no match status authorization access to this api is granted via an authorization token, ensuring secure and authenticated access for authorized users sample curl preproduction curl location 'https //api preproduction signzy app/api/v3/global kyc verify/mx/curp' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "firstname" "juan jose", "fatherlastname" "torres", "motherlastname" "lopez", "dateofbirth" "1980 01 01", "gender" "male ", "identityinformation" { "nationalidnumber" "petj970221xxxxxx00" }, "consent" true } ' production curl location 'https //api signzy app/api/v3/global kyc verify/mx/curp' \\ \ header 'authorization \<auth token>' \\ \ header 'content type application/json' \\ \ data '{ "firstname" "juan jose", "fatherlastname" "torres", "motherlastname" "lopez", "dateofbirth" "1980 01 01", "gender" "male ", "identityinformation" { "nationalidnumber" "petj970221xxxxxx00" }, "consent" true } ' api input { "firstname" "\<first name>", "fatherlastname" "\<father's last name>", "motherlastname" "\<mother's last name>", "dateofbirth" "\<dob>", "gender" "\<gender> ", "identityinformation" { "nationalidnumber" "\<mexico curp id>" }, "consent" true } request body parameters parameter type description required/optional firstname string the first name of the person required fatherlastname string the father's last name of the person required motherlastname string the mother's last name of the person required dateofbirth string date of birth of the person in yyyy mm dd format required gender string gender of the person male/female optional nationalidnumber string 18 character alphanumeric curp id number required consent boolean consent of the end user for verification of his/her data required response { "result" { "verificationresult" { "firstname" true, "fatherlastname" true, "motherlastname" true, "dateofbirth" false, "gender" true, "nationalidnumber" true } } } response body parameters parameter description data type firstname the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean fatherlastname the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean motherlastname the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean gender the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean dateofbirth the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean nationaidnumber the api returns a boolean value ("true" for a match found and "false" for no match found) based on the verification of the provided input data against authorized sources boolean error code and response mapping 400 (bad request) { "error" { "name" "error", "message" "bad input and description ", "status" 400, "reason" "validation error", "type" "bad request", "statuscode" 400 } } 401(unauthorized) { "error" { "name" "error", "message" "invalid authentication credentials", "status" 401, "reason" "authentication error", "type" "bad request", "statuscode" 401 } } 403 (forbidden) { "error" { "name" "error", "message" "forbidden", "reason" "error", "type" "bad request", "statuscode" "403" } } 500 (internal server error) { "error" { "name" "error", "message" "internal server error", "status" 500, "reason" "error", "type" "bad request", "statuscode" 500 } } 409(upstream down { "error" { "name" "error", "message" "upstream down", "status" 409, "reason" "error", "type" "bad request", "statuscode" 409 } } field type description name string text displayed on the screen explaining error type reason string reason for the error status number http status code message string error message indicating an upstream error type string error type statuscode number status code representing the error scenario getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!