Mobility · Hurlingham # Traffic fines in Hurlingham: what the API returns and what the data shows Which fines Hurlingham issues, why almost no lookup finds one, what our data from the last year shows and how a western-suburbs fleet queries the municipal court by plate. ![](/img/autores/enrique-orione/photo-240.2526eefb2549.webp)By [Enrique Orione](https://apinitro.com/en/authors/enrique-orione/)September 15, 2026 ![A street of English-style houses with thick trees and a lit street lamp](/img/articulos/ar-traffic-fines-ar-b-hurlingham/hero-1200.788c6cd2ab07.webp) Jurisdiction Hurlingham (Buenos Aires) · [Buenos Aires](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/) · Argentina Hurlingham is a residential partido in the western suburbs, between Morón, Ituzaingó and San Miguel: Vergara and Jauretche avenues, the Camino del Buen Ayre on its edge and the tree-lined streets of Villa Tesei and William Morris carry mostly private cars, deliveries and services. Municipal fines are issued by the partido on avenues and camera-equipped traffic lights; provincial ones coexist on the same plates. ## Context and authority Like every partido in Buenos Aires, it applies the [National Traffic Law 24.449](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto) through the provincial adhesion: fixed-unit amounts, a two-year limitation for minor offences and five for serious ones, and a defence before the court that issued the fine. Provincial fines are covered in the [Buenos Aires article](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/). The municipal misdemeanour court rules on Hurlingham fines: red lights and right of way at the camera-equipped intersections of Vergara and Jauretche avenues, speeding on the access avenues and lanes and manoeuvres downtown. A defence is filed with the court within the period set by the notice. ## What the API returns for this jurisdiction In Hurlingham the API queries the Hurlingham municipal misdemeanour court and, in the same lookup, the other integrated sources of Buenos Aires; it 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. The response splits the result by source: the Hurlingham court and the provincial sources answer separately, and the partial-result flag shows whether any failed to answer. ## What the data shows Proprietary data**Hurlingham**September 1, 2025 – August 31, 2026 Lookups with at least one open fine 1% Fines offering voluntary early payment 25% Median age of fines without a recorded resolution 190 days Median amount band ARS 250,000 – ARS 500,000 Mix by infraction category 1. Speeding25% 2. Red light and right of way53% 3. Lanes and manoeuvres22% 4. Other infractions0% Monthly distribution of fines 1. Jan11% 2. Feb8% 3. Mar6% 4. Apr13% 5. May23% 6. Jun10% 7. Jul– 8. Aug– 9. Sep10% 10. Oct4% 11. Nov7% 12. Dec9% Sample: 100–500 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/) Only 1% of the plate lookups in the period found a Hurlingham fine without a recorded resolution: the lowest share among the partidos we publish. It is a residential partido most people who look up do not cross, and the sample of fines is small, between one hundred and five hundred. More than half of the fines observed are for red lights and right of way; speeding and lanes and manoeuvres split the rest almost equally. The median amount band is ARS 250,000 – ARS 500,000 and the median age of open fines is 190 days, among the lowest we publish. Only 25% of the fines offered voluntary payment at lookup time, the lowest share in the suburbs in our data: in Hurlingham a fine discovered by lookup is almost always already at full amount. ## Case study: fleets that look up plates in Hurlingham Proprietary data**Fleet cohort**September 1, 2025 – August 31, 2026 Fleet accounts in the sample 50 Distinct plates looked up by fleets 2,040 Sample: 100–500 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, had fewer than fifty lookups with a Hurlingham fine, the floor the [data methodology](https://apinitro.com/en/data-methodology/) requires to publish a share; the figure exists, but it is not published below that threshold. For a service company based in the west, with technicians covering Hurlingham between Morón and San Miguel, the risk is not volume but the full amount: a plate lookup thirty days after each month, with the per-source result stored, assigns the fine to the technician and avoids paying it without a discount when it shows up at the technical inspection. ## 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-hurlingham" ] } ``` 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 - The Hurlingham sample of fines is small; the shares read as orders of magnitude, not fine figures. - 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 Hurlingham](https://www.hurlingham.gob.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-hurlingham) ## 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-c/hero-640.6862f884394b.webp) Mobility ## Traffic fines in Buenos Aires City: what the API returns and what the data shows The city’s voluntary-payment window lasts forty days; our data shows fines with a much older median age. How to look them up through the API and act in time. Read article ↗](https://apinitro.com/en/articles/traffic-fines-buenos-aires-city/) [ 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/)