Río Tercero is an industrial city in central Córdoba: the petrochemical complex, the military factory and the metalworking plants move trucks and pickups along Provincial Route 6, which links it with Villa María and with the reservoirs and the hills, and along the access to Route 36 at Almafuerte towards the capital and Río Cuarto. Municipal fines are issued by the city; route fines are issued by the provincial Policía Caminera and coexist on the same plates.

Context and authority

Amounts and deadlines follow the National Traffic Law 24.449 and Córdoba’s adhesion: fixed units, a two-year limitation for minor offences and five for serious ones, a defence before the authority that issued the fine. This article covers municipal fines; the provincial circuit is in the Córdoba article.

The municipal misdemeanour court rules on fines issued within the city: speeding on the access avenues and the urban stretch of Route 6, red lights at camera-equipped crossings and parking downtown. A defence is filed with the court within the period set by the notice; fines on Route 6 and Route 36 outside the town limits belong to the Policía Caminera, as the Córdoba article describes.

What the API returns for this jurisdiction

In Río Tercero the API queries the Río Tercero municipal misdemeanour court and, in the same lookup, the other integrated sources of Córdoba; it returns each fine with the authority that issued it:

  • The authority that issued the fine and its number, unnormalised.
  • The date and description of the infraction, with the location if the court reports it.
  • The amount and status current at the source, with the payment conditions it publishes.
  • The link to the payment slip 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 Río Tercero

Manual verification starts at the Río Tercero municipal portal, continues through the provincial circuit of the Córdoba article and ends at the ANSV national lookup. That round, repeated for every plate, 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 Río Tercero

A truck fleet going in and out of the petrochemical complex crosses the urban stretch of Route 6 with municipal checks and, a few kilometres on, those of the Policía Caminera; the same plate lookup returns both fines separately, and running it at month end, with the per-source result stored, assigns each fine to the driver and covers the defence in time.

For a service company with pickups going from Río Tercero to the reservoirs and the hills at weekends, the Caminera fines are the expensive ones and the municipal ones the frequent ones; reading the result per source avoids mixing two circuits with different deadlines.

How to integrate

The integration starts with one POST per plate, with the jurisdiction as an optional filter. Since courts 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": "ABC123",
  "jurisdictions": [
    "AR-X-rio-tercero"
  ]
}

Limits and considerations

  • Fines on national and provincial routes outside the town limits are not municipal; the response names the authority of each.
  • Fixed-unit amounts are converted at the value current at the source; 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 defences; it delivers information to decide.

Sources and further reading