Río Negro holds three provinces within it: the fruit-growing and oil Alto Valle along National Route 22, with General Roca and Cipolletti; the Atlantic coast of Viedma and San Antonio Oeste along Route 3; and the Andes of Bariloche along Routes 40 and 23. Each corridor has its own municipal misdemeanour courts and checks; the routes depend on the provincial road-safety authority.

Context and authorities

The framework is the National Traffic Law 24.449: fines in fixed units, a two-year limitation for minor offences and five for serious ones, and a defence before the court that issued the fine. The Río Negro Government portal gathers official information.

The Alto Valle rules on its fines at the misdemeanour courts of General Roca, Cipolletti, Villa Regina and Cinco Saltos, with speed cameras on Route 22 and on the access avenues; Viedma, San Antonio Oeste and Las Grutas cover the coast, and Bariloche and El Bolsón the Andes, with checks reinforced in the snow and summer seasons. On Routes 22, 3, 23 and 40 fines are issued by the provincial road-safety authority. A defence is filed with the court that issued the fine.

What the API returns for this jurisdiction

In Río Negro the API currently queries the municipal misdemeanour courts of Viedma, Cinco Saltos, San Antonio Oeste and Darwin and 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 Negro

To check a plate by hand, the ANSV national lookup lists the fines loaded by participating authorities and the Río Negro Government portal points to each municipal court. The API does the same at scale: it walks the integrated authorities by plate and returns the fines with their origin, so verification becomes part of the process rather than a spreadsheet.

What to watch if you run a fleet in Río Negro

An Alto Valle fruit or oil service pickup crosses Cipolletti, Roca and Villa Regina along Route 22 in a single day and answers to different courts for the same stretch; since each one publishes at its own pace, the plate lookup is worth repeating thirty and sixty days later, storing the per-source result.

In the Andes the peak is the snow season in Bariloche, when rental vehicles and checks at the entrances to the ski hill add up; a rent-a-car that checks the plate at return, with the result stored, charges the fine to the right customer instead of absorbing it when renewing the technical inspection.

How to integrate

A lookup is a POST with the plate and, optionally, the jurisdictions to include; the initial response accepts the job and the result arrives by status lookup or webhook, because official sources answer in seconds or minutes. The asynchronous APIs guide explains how to retry without duplicating work and the API page details access.

JSONIllustrative example, not a contract.
{
  "plate": "ABC123",
  "jurisdictions": [
    "AR-R"
  ]
}

Limits and considerations

  • The three corridors publish at different rhythms; the fine date takes precedence over the lookup date.
  • 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