The O'Higgins Region is an hour from Santiago on the concessioned Route 5: Rancagua and Machalí live off the El Teniente mine and its contractors, San Fernando and the Colchagua valley off fruit and wine, and Rengo and Graneros off the agro-industry supplying the capital. Many Santiago fleets cross it daily. Each comuna has its local police court, Carabineros issues fines on the routes and the cameras and gantries register by plate in the Civil Registry.

Context and authorities

Traffic fines are sanctions applied by the local police court of each comuna under Law 18.290, with amounts in monthly tax units according to the seriousness of the infraction; those on motorways and highways are issued by Carabineros, and the cameras and gantries of a concessioned motorway generate complaints that arrive by post. An unpaid fine is entered in the Civil Registry’s register and blocks the circulation permit until it is paid.

The local police courts of Rancagua, San Fernando, Rengo and Machalí rule on the fines of their comunas, with enforcement at the mine approaches and downtown; the Route 5 concessionaire reports unpaid passes to the court of the gantry’s comuna and Carabineros issues speeding fines on the Carretera del Cobre. Registered fines block the circulation permit until they are paid.

What the API returns for this jurisdiction

In the O'Higgins Region a plate is sent to the Chile fines API, which walks its integrated sources and returns each fine with the authority that recorded it:

  • Court or authority and case number or fine number exactly as the source publishes them.
  • Date, comuna and article infringed when the source reports it.
  • Amount in tax units and pesos, with the current status.
  • Coverage per source and a partial-result flag when any failed to answer.

How to check a plate in the O'Higgins Region

Manual verification starts at the Civil Registry’s Register of Unpaid Fines, which concentrates the registered fines of the whole country, and continues at the local police court of the comuna for those that summon the driver. That round, repeated for every unit, is what the API replaces: one lookup per plate across the integrated sources, with the result per source.

What to watch if you run a fleet in the O'Higgins Region

A fleet of El Teniente contractors sending pickups and shift buses up the Carretera del Cobre piles up Carabineros fines and those of the Rancagua and Machalí courts on units that change crew every shift; looking up each plate at month end, with the result stored per authority, lets you assign them while the shift record exists.

For a Santiago company whose trucks descend to Colchagua for the grape harvest, the monthly plate lookup finds the gantry complaints before they are registered and block the circulation permit.

How to integrate

The integration starts with one POST per vehicle, with the jurisdiction 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 limits and fields.

JSONIllustrative example, not a contract.
{
  "plate": "BBBB10",
  "jurisdictions": [
    "CL-LI"
  ]
}

Limits and considerations

  • Fines with a summons to the driver are processed at the corresponding local police court and are not always entered in the plate register.
  • Amounts in monthly tax units are converted at the value of the month of payment; the final amount is set by the court.
  • A source that does not answer is reported as such, never as an absence of fines.
  • The API neither pays fines nor files defences; it delivers information to decide.

Sources and further reading