Mobility · Lomas de Zamora # Traffic fines in Lomas de Zamora: what the API returns and what the data shows Which fines Lomas de Zamora issues, why speeding dominates, what our data from the last year shows and how a fleet queries the municipal court by plate. ![](/img/autores/francisco-orione/photo-240.ff6c48f047e6.webp)By [Francisco Orione](https://apinitro.com/en/authors/francisco-orione/)September 15, 2026 ![A cobbled passage with trees and warm-lit street lamps](/img/articulos/ar-traffic-fines-ar-b-lomas-de-zamora/hero-1200.aa800392de60.webp) Jurisdiction Lomas de Zamora (Buenos Aires) · [Buenos Aires](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/) · Argentina Lomas de Zamora concentrates the traffic of the southern suburbs: Hipólito Yrigoyen avenue and Camino Negro, Provincial Route 4 (Camino de Cintura) and the La Noria bridge connect it with the City, with La Matanza and with the south of the province, with speed and red-light cameras on the main corridors. Municipal fines are issued by the partido; provincial ones overlap on the same plates. ## Context and authority The partido adheres to the [National Traffic Law 24.449](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto) through the provincial law: fines are expressed in fixed units and lapse after two years if minor and five if serious. Municipal fines are ruled on by the partido’s misdemeanour court; those issued by the province follow their own circuit, described in the [Buenos Aires article](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/). The municipal misdemeanour court rules on fines issued within the partido: speeding on Camino Negro and Hipólito Yrigoyen avenue, red lights at camera-equipped intersections, parking in downtown Lomas and in Banfield, and lanes at the access roads. A defence is filed with the court within the period set by the notice. ## What the API returns for this jurisdiction A plate lookup in Lomas de Zamora walks the Lomas de Zamora municipal misdemeanour court together with the integrated provincial sources of Buenos Aires, and returns each fine with the authority that issued it: - Authority and fine number exactly as each court publishes them. - Date, location when reported and description of the infraction. - Amount, status and payment conditions published by that court. - Downloadable payment slip when one exists. - Coverage per source and partial-result flag. A result with no fines at the municipal court does not rule out provincial fines on the same plate; the response reports which sources were queried and which answered. ## What the data shows Proprietary data**Lomas de Zamora**September 1, 2025 – August 31, 2026 Lookups with at least one open fine 9% Fines offering voluntary early payment 38% Median age of fines without a recorded resolution 240 days Median amount band ARS 250,000 – ARS 500,000 Mix by infraction category 1. Speeding47% 2. Red light and right of way27% 3. Parking24% 4. Lanes and manoeuvres10% 5. Other infractions0% Monthly distribution of fines 1. Jan14% 2. Feb12% 3. Mar15% 4. Apr9% 5. May5% 6. Jun3% 7. Jul1% 8. Aug0% 9. Sep11% 10. Oct6% 11. Nov6% 12. Dec17% Sample: 1.000–5.000 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/) 9% of the plate lookups in the period found at least one Lomas de Zamora fine without a recorded resolution: the highest share among the southern partidos we publish, consistent with a transit partido with speed cameras on its corridors. Almost half of the fines observed are for speeding; red lights and parking split most of the rest. The median amount band is ARS 250,000 – ARS 500,000 and the median age of open fines is 240 days. Only 38% of the fines offered voluntary payment at lookup time: in Lomas, unlike Lanús or Ezeiza, most of the fines we found no longer had a discount available, which makes discovering them late more expensive. ## Case study: fleets that look up plates in Lomas de Zamora Proprietary data**Fleet cohort**September 1, 2025 – August 31, 2026 Fleet lookups with at least one open fine 11% Fleet accounts in the sample 50 Distinct plates looked up by fleets 2,040 Sample: 1.000–5.000 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/) The fleet cohort, 50 accounts with twenty or more plates and 2,040 plates in total, found at least one Lomas fine in 11% of its lookups, above the general public: fleets travel the camera corridors more than the average driver. For a passenger transport or logistics company that uses Camino Negro every day, the reading is direct: look up each plate at month end and, above all, before the defence deadlines expire, because in this partido a fine that shows up late rarely keeps its discount. ## 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](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/) guide describes. The [API page](https://apinitro.com/en/apis/traffic-fines-argentina/) details access. JSONIllustrative example, not a contract. ```json { "plate": "ABC123", "jurisdictions": [ "AR-B-lomas-de-zamora" ] } ``` The result arrives split by authority: a municipal court with no fines says nothing about the provincial source or the neighbouring municipalities, and the partial-result flag shows whether any source failed to answer. ## Limits and considerations - Speeding fines from Camino Negro and Hipólito Yrigoyen avenue are served on the registered owner; a unit whose owner lives outside the partido discovers them by lookup before by mail. - 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. - Proprietary data comes from user lookups, not from a registry: the share of fines is skewed towards suspect plates. - 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 - [Municipalidad de Lomas de Zamora](https://www.lomasdezamora.gov.ar/) - [Ley Nacional de Tránsito 24.449 — texto actualizado](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto) - [Agencia Nacional de Seguridad Vial — Consulta nacional de infracciones](https://consultainfracciones.seguridadvial.gob.ar/) Related API ## [Argentina traffic fines API](https://apinitro.com/en/apis/traffic-fines-argentina/) Bring vehicle fine checks into fleet operations, vehicle transactions and document review workflows. [Ask about this API](https://apinitro.com/en/contact/?api=ar.mobility.traffic-fines&ref=article:ar-traffic-fines-ar-b-lomas-de-zamora) ## Related articles [![](/img/articulos/ar-traffic-fines-ar-b/hero-640.e7b8a039b11b.webp) Mobility ## Traffic fines in Buenos Aires Province: what the API returns and what the data shows Two layers of authorities, one plate: how to look up provincial and municipal fines through the API and what a year of our data shows. Read article ↗](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/) [![](/img/articulos/ar-traffic-fines-ar-b-lanus/hero-640.184a670a483a.webp) Mobility ## Traffic fines in Lanús: what the API returns and what the data shows Which fines Lanús issues, what our data from the last year shows and how a fleet in the southern suburbs queries the municipal court and the provincial source in a single call. Read article ↗](https://apinitro.com/en/articles/traffic-fines-lanus/) [ 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/)