Address Validation in Mexico via API

Professional accuracy for your logistics, financial, and operational processes.

Are your Mexico addresses truly reliable?

In Mexico, address data quality can make the difference between a successful delivery and an unhappy customer.
Issues like duplicated neighborhoods (colonias), inconsistent postal codes, or misspelled street names create
hidden costs, delays, and compliance risks.

The MexicoGISData Address Validation API (AV API) is built specifically for the Mexican market
to validate, verify, and standardize addresses against the most complete and up-to-date database available.

API_ENGLISH

An approach designed for Mexico’s reality

Our service does not try to “guess” or correct invalid addresses. Instead, it follows a clear and reliable process:

Compare the input address against the validated MexicoGISData database.
Check whether there’s a match in postal and geographic reality.
Respond with a structured result, including a match level (Exact, Strong, Medium, etc.).
Continuously update the database so you always work with the latest version.

The outcome: standardized, trustworthy, and ready-to-use information for logistics, e-commerce,
banking, insurance, government, and more.

Simple to integrate, easy to use

Required parameters

state – State
street – Street name
hse_nmb – House/External number
set_name – Settlement / neighborhood (colonia)
cp – Postal code
city – City
country – Default: MÉXICO

With just these fields you can obtain a reliable result.

Best practices for better results

Use simple state names: “CIUDAD DE MÉXICO,” not “CDMX.”
Don’t include street types: “INSURGENTES SUR,” not “Av. Insurgentes Sur.”
Prefer simple city names: “DURANGO” instead of “VICTORIA DE DURANGO.”
Use settlement names without prefixes: “DEL VALLE,” not “Col. Del Valle.”

What you’ll get

Each request returns a structured response including:

Result status (found, not_found, ambiguous).
Achieved match level.
Fields that matched and those that did not.
Validated, standardized data (with LAT/LON coordinates).
Package usage information and plan validity.

Available Matching Levels

Match Level	Mandatory Fields	Optional Fields	Notes
1. Exact Match	State, Street, House Number, Settlement, Postal Code	None	All provided → unique match. Settlement+CP must be consistent.
2. Strong Match	State, Street, House Number, Postal Code	Settlement	If Settlement is missing or does not match CP, return all settlements for that CP.
3. Medium Match	State, Street, House Number, Settlement	Postal Code	Settlement determines CP. Risk of street name duplicates across settlements.
4. Medium2 Match	State, Street, Postal Code (partial allowed)	House Number, Settlement	Matches using postal code (even partial). Useful when house numbers or settlement are missing/inconsistent.
5. Weak Match	State, Street, House Number	Settlement, Postal Code	Returns all possible settlements/colonias in the state for that street + house number.
6. Very Weak Match	State, Street	House Number, Settlement, Postal Code	Broad search. Flag “status”:”ambiguous”.
7. Not Found	None	None	No match found. “status”:”not_found”.

Easy access

Each customer receives:

A unique API Key for authentication.
A prepaid query package valid for 12 months.
Technical support for integration and additional questions.

Implementation is immediate with a clear GET structure for your developers.

Plans & Pricing

Package	Included Queries	Price per query	Total USD	Validity
Starter	5,000	$0.040 (4.0¢)	$200	12 months
Basic	10,000	$0.035 (3.5¢)	$350	12 months
Standard	50,000	$0.025 (2.5¢)	$1,250	12 months
Pro	100,000	$0.020 (2.0¢)	$2,000	12 months
Business	250,000	$0.018 (1.8¢)	$4,500	12 months
Enterprise	500,000	$0.015 (1.5¢)	$7,500	12 months
Corporate	1,000,000	$0.010 (1.0¢)	$10,000	12 months
Custom	1M+ queries	Call us	—	12 months

Ready to try it?

Request a personalized demo and see how the MexicoGISData AV API can improve the reliability of your address data and optimize your processes.