Mexicali is the capital of Baja California and a border and valley city: the crossings to Calexico, the maquiladoras, the farming valley and federal highways 2, towards Tijuana and San Luis Río Colorado, and 5, towards San Felipe, move export trucks, farm pickups and heavy urban traffic under extreme heat. The municipality runs its traffic and its infractions; the state collects debts with plate 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 gob.mx procedures portal of the Government of Mexico.

The Dirección de Seguridad Pública Municipal, through its traffic unit, issues and collects infractions in the city and the valley; the Guardia Nacional and the federal authority issue them on highways 2 and 5, and the state’s Secretaría de Hacienda collects vehicle debts together with plate renewal. Clarifications are filed with the authority that recorded the infraction, within the period set by the notice.

What the API returns for this entity

A plate lookup in Mexicali walks Mexicali’s municipal plate lookup for infractions and returns each infraction with the authority that recorded 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 Mexicali

A plate is checked by hand at the gob.mx procedures portal of the Government of Mexico and, for the vehicle’s identity, at the REPUVE. The API does the same round at scale and returns each infraction with the authority that recorded it, so verification becomes part of the fleet process rather than a spreadsheet.

What to watch if you run a fleet in Mexicali

An export fleet crossing to Calexico several times a day travels Mexicali’s boulevards with municipal checks on every trip, and infractions pile up on plates that rotate among operators; looking up each plate at month end, with the per-source result stored, assigns each infraction to the driver and avoids discovering them at plate renewal.

For a farming company in the valley with pickups going from the fields to the city, municipal infractions show up weeks later; a plate lookup before plate renewal and at the close of each season covers clarifications in time.

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.

JSONIllustrative example, not a contract.
{
  "plate": "ABC123A",
  "jurisdictions": [
    "MX-BCN-mexicali"
  ]
}

Limits and considerations

  • Infractions on federal highways belong to the federal authority, not the state or municipal ones; the response names the authority of each.
  • 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.

Sources and further reading