Treinta y Tres is the heart of Uruguayan rice: the Laguna Merín basin and the city’s mills move grain trucks from autumn, Route 8 crosses it towards Melo and Montevideo, and Routes 17 and 19 connect it with Río Branco and Rocha; the Quebrada de los Cuervos attracts growing nature tourism. Urban fines are issued by the Intendencia and collected through SUCIVE together with the vehicle tax; those on the routes, by the Policía Caminera.

Context and authorities

The framework is Law 18.191 on Traffic and Road Safety, which defines the infractions and expresses fines in adjustable units, and each intendencia applies them in its department through its transit office; on national routes the Policía Caminera acts. Fine debts are collected together with the vehicle tax through SUCIVE, the single system that unified collection across the nineteen departments, and they block the transfer and the renewal of the vehicle booklet.

The Intendencia’s Transit Directorate issues fines in Treinta y Tres, Vergara and Santa Clara de Olimar, with load and speed checks on the urban stretch of Route 8 during the harvest; a defence is filed with the Intendencia and payment is made through SUCIVE or at its offices. Caminera fines on Routes 8 and 17 are also collected through SUCIVE.

What the API returns for this jurisdiction

In Treinta y Tres a plate is sent to the Uruguay fines API, which walks its integrated sources and returns each fine with the authority that applied it:

  • Intendencia or authority and fine number exactly as the source publishes them.
  • Date, location when reported and article infringed.
  • Amount in adjustable units and pesos, with the status current at the source.
  • Coverage per source and a partial-result flag when any failed to answer.

How to check a plate in Treinta y Tres

Manual verification starts at SUCIVE, which unifies tax and fine debts of the nineteen departments, and continues at the Treinta y Tres Intendencia portal for the detail of each fine and the defence. 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 Treinta y Tres

A rice fleet taking grain from the farms to the mills and from the mills to the port during the harvest piles up Caminera load fines and those of the Treinta y Tres, Cerro Largo and Rocha intendencias on trucks rotating between drivers; looking up each plate at month end, with the result stored per authority, lets you assign them to the trip’s driver.

For a mill with its own fleet, the plate lookup before each vehicle-tax instalment prevents a forgotten harvest fine from blocking the payment at the busiest time.

How to integrate

A lookup is a POST with the identifier 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 lookups, and the API page describes the full contract.

JSONIllustrative example, not a contract.
{
  "plate": "SBC1234",
  "jurisdictions": [
    "UY-TT"
  ]
}

Limits and considerations

  • Fines from the Policía Caminera on national routes are processed by the Ministry of the Interior and are also collected through SUCIVE.
  • Amounts in adjustable units are converted at the current value; the final amount is set by the intendencia at the time of payment.
  • A source that does not answer is reported as such, never as an absence of fines.
  • The API neither pays fines nor handles defences; it delivers information to decide.

Sources and further reading