Coahuila has three regions that work almost like three states: Saltillo and Ramos Arizpe, with the automotive industry and Highway 57 descending to Monterrey and Querétaro; the Laguna region of Torreón, joined to Durango by Highway 40; and the border of Piedras Negras and Acuña facing Texas. Along those routes travel auto-parts trailers, supplier pickups and staff transport. Infractions are issued by the municipal transit offices in the cities and by the state authority on the highways; debts are collected with the state renewal.
Context and authorities
The framework is the entity’s traffic regulation and, on federal roads, the federal regulation: fines are expressed as multiples of the Unidad de Medida y Actualización (UMA) and collected as tax credits, with late surcharges. Many vehicle procedures, such as emissions verification or plate renewal, require having no pending infractions. Institutional information is on the Coahuila Government portal.
Saltillo, Torreón, Monclova and the border cities each have their own transit office and regulation, with different early-payment discounts; the state police issues infractions on the state highways and the National Guard on federal 57 and 40. The state fiscal administration adds debts to the vehicle control and conditions the renewal, the change of ownership and the cancellation on paying final infractions.
What the API returns for this entity
In Coahuila a plate lookup walks the integrated sources of the Mexico fines API and returns each infraction with the authority that recorded it, as the source publishes it:
- The authority that recorded the infraction and its folio, unnormalised.
- The date and reason, with the location if the source reports it.
- The amount and status current at the source, with the discounts it publishes.
- The payment reference when the authority offers one.
- Which sources answered and which did not, to tell a complete result from a partial one.
How to check a plate in Coahuila
Manual verification starts at the Coahuila Government portal and is completed with the citizen lookup of the REPUVE, which confirms plate, serial number and theft report. That round, repeated for every unit, is what the API replaces: one lookup per plate across the integrated sources, with the result per source so you know what was verified.
What to watch if you run a fleet in Coahuila
A fleet of automotive suppliers travelling from Ramos Arizpe to the plants in Nuevo León and back on Highway 57 piles up state and municipal infractions from two states on units that rotate between drivers; the notice reaches the company in batches. Looking up each plate at month end, with the result stored per authority, sorts out that mix and lets you assign each infraction to the driver on shift.
For a staff transport company in the Laguna region, the plate lookup before renewing the registration of the whole fleet prevents a forgotten debt from leaving units off the road in the season of highest demand.
How to integrate
The integration starts with one POST per plate, with the entity as an optional filter. Since sources answer at their own pace, the API accepts the job and delivers the result by status or webhook; store the idempotency key before sending, as the asynchronous APIs guide describes. The API page details access.
{
"plate": "ABC123A",
"jurisdictions": [
"MX-COA"
]
}Limits and considerations
- Infractions on federal highways are issued by the National Guard and paid separately from state debts.
- UMA amounts are updated every year; the final amount is set by the authority at the time of payment.
- A source that does not answer is reported as such, never as an absence of infractions.
- The API neither pays fines nor handles clarifications; it delivers information to decide.
