Baja California lives off the border: Tijuana and Tecate facing California, Mexicali as capital and Ensenada as port, joined by the scenic highway and Highway 2 that carry maquiladora traffic, freight heading to the crossings and a fleet of imported cars with border plates. Infractions are issued by the municipal transit offices and by the state authority on the highways, and debts are collected together with the state’s renewal and vehicle control. Mexicali has its own municipal lookup, covered in its own article.

Context and authorities

Infractions are sanctioned under the state traffic regulation, with amounts set in Unidades de Medida y Actualización (UMA) and updated every year; unpaid ones accumulate as vehicle debts and block procedures such as plate renewal, change of ownership or verification. The Baja California Government portal publishes official information.

Each municipality, from Tijuana to Ensenada, issues the infractions on its streets through its transit office and collects them at its treasury; those on state highways depend on the state authority, and those on federal Highway 2 and the federal stretches on the National Guard. The state collects the annual vehicle control and does not release it with final pending infractions, which turns each renewal into the moment forgotten fines show up.

What the API returns for this entity

In Baja California a plate is sent to the Mexico fines API, which walks its integrated sources 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 Baja California

Manual verification starts at the Baja California 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 Baja California

Maquiladora and cross-border transport fleets cross Tijuana and Tecate several times a day with units rotating between drivers; a municipal infraction in Tijuana and a state one on the scenic highway arrive through different channels and on different dates. Looking up each plate at month end, with the result stored per authority, lets you assign them to the driver while the crossing record exists.

For a rent-a-car in Tijuana or Ensenada delivering cars to visitors from California, the plate lookup at the return of each rental is the difference between charging the infraction to the customer and absorbing it when renewing the vehicle control.

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"
  ]
}

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.

Sources and further reading