Mobility · Cerro Largo # Traffic fines in Cerro Largo: intendencia, SUCIVE and API lookups How traffic fines work in Cerro Largo, which authorities apply them and how a fleet checks its plates and queries them by API. ![](/img/autores/francisco-orione/photo-240.ff6c48f047e6.webp)By [Francisco Orione](https://apinitro.com/en/authors/francisco-orione/)September 16, 2026 ![An international stone bridge over a border river with warm lamps at blue hour](/img/articulos/uy-traffic-fines-uy-cl/hero-1200.38d0470d2ca9.webp) Jurisdiction Cerro Largo Department · Uruguay Cerro Largo looks towards Brazil: Melo, the capital, sits on Route 8 coming from Montevideo and Route 26 crossing towards Tacuarembó, and Río Branco joins Jaguarão by the Barón de Mauá international bridge, with duty-free shops and border trade. Rice and cattle move trucks all year and Brazilian plates are part of the landscape. Urban fines are issued by the Intendencia and collected through SUCIVE; those on the routes, by the Policía Caminera. ## Context and authorities The framework is [Law 18.191 on Traffic and Road Safety](https://www.impo.com.uy/bases/leyes/18191-2007), 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](https://www.sucive.gub.uy/), 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 Melo, Río Branco and Fraile Muerto, with checks at the accesses and in the duty-free area; a defence is filed with the Intendencia and payment is made through SUCIVE or at its offices. Fines on Brazilian vehicles are collected on the spot and those on Route 8 outside the cities are issued by the Policía Caminera. ## What the API returns for this jurisdiction In Cerro Largo a plate is sent to the [Uruguay fines API](https://apinitro.com/en/apis/traffic-fines-uruguay/), which walks its integrated sources and returns each fine with the authority that applied it: - The authority that applied the fine and its number, unnormalised. - The date and reason, with the location if the source reports it. - The amount and status current at the source. - Which sources answered and which did not, on every lookup. The response reports which sources were queried and which answered; for Cerro Largo, the official channel for debts is SUCIVE and the intendencia portal, described below, and a result with no fines in the integrated sources does not rule out debts recorded there. ## How to check a plate in Cerro Largo A plate is checked by hand at [SUCIVE](https://www.sucive.gub.uy/) and, for the detail and the defence, at the [Cerro Largo Intendencia portal](https://www.cerrolargo.gub.uy/). The API does the same round at scale and returns each fine with the authority that applied it, so verification becomes part of the fleet process rather than a spreadsheet. ## What to watch if you run a fleet in Cerro Largo A rice fleet descending Route 8 towards the mills and the port piles up Caminera fines and those of several eastern 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 while the delivery note exists. For a Río Branco company with units crossing the bridge daily, the plate lookup before paying the vehicle tax separates Uruguayan debts from Brazilian infractions, which follow another circuit. ## 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](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/) guide describes. The [API page](https://apinitro.com/en/apis/traffic-fines-uruguay/) details limits and fields. JSONIllustrative example, not a contract. ```json { "plate": "SBC1234", "jurisdictions": [ "UY-CL" ] } ``` ## 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 - [Intendencia de Cerro Largo — portal oficial](https://www.cerrolargo.gub.uy/) - [SUCIVE — Sistema Único de Cobro de Ingresos Vehiculares](https://www.sucive.gub.uy/) - [Unidad Nacional de Seguridad Vial (UNASEV)](https://www.gub.uy/unidad-nacional-seguridad-vial/) - [Ley 18.191 de Tránsito y Seguridad Vial — IMPO](https://www.impo.com.uy/bases/leyes/18191-2007) Related API ## [Uruguay traffic fines API](https://apinitro.com/en/apis/traffic-fines-uruguay/) Add Uruguayan fine lookups to vehicle documentation reviews and fleet workflows. [Ask about this API](https://apinitro.com/en/contact/?api=uy.mobility.traffic-fines&ref=article:uy-traffic-fines-uy-cl) ## Related articles [![](/img/articulos/uy-traffic-fines-uy-tt/hero-640.c59b53644ef4.webp) Mobility ## Traffic fines in Treinta y Tres: intendencia, SUCIVE and API lookups How traffic fines work in Treinta y Tres, which authorities apply them and how a fleet checks its plates and queries them by API. Read article ↗](https://apinitro.com/en/articles/traffic-fines-treinta-y-tres/) [ Mobility ## How to assess the quality of a vehicle lookup A useful vehicle lookup explains what was observed, where and when. These questions help teams turn records into clear product decisions. Read article ↗](https://apinitro.com/en/articles/vehicle-data-quality/) [ Integrations ## Asynchronous APIs: retry without duplicating work A connection can fail after work has already started. Designing around the operation makes recovery clearer for users and integrations. Read article ↗](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/) [← All articles](https://apinitro.com/en/articles/)