San Juan moves mining pickups towards the Andean projects, wine-industry trucks and traffic towards Chile through the Agua Negra pass, almost all along National Route 40 and Routes 20 and 141 towards the east. Urban infractions are ruled on by the municipal misdemeanour courts of Greater San Juan; route infractions depend on the provincial traffic and 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 San Juan Government portal gathers official information.

Greater San Juan splits its urban fines among the misdemeanour courts of the capital, Rawson, Rivadavia, Chimbas and Santa Lucía, with camera fines on the ring avenue and at the entrances; Jáchal, Caucete and the interior departments have their own courts. On Route 40, on Route 20 towards San Luis and on Route 150 towards the Agua Negra pass, fines are issued by the provincial traffic and road-safety authority, with Gendarmería checks along the international corridor. A defence is filed with the authority that issued the fine.

What the API returns for this jurisdiction

For San Juan, every plate lookup returns the fines reported by the queried authorities, with the authority that issued them:

  • 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 San Juan

Manual verification starts with the ANSV national lookup and continues on the San Juan Government portal and at the municipal courts. That round, repeated for every plate, is what the API replaces: one lookup per plate across the integrated authorities, with the result split by source so you know what was verified and what was not.

What to watch if you run a fleet in San Juan

Andean mining project pickups and wine-industry trucks pass checks on Route 40 and at the entrances to Greater San Juan that issue fines ruled on far from the vehicle’s base; by the time the notice arrives, the unit has already rotated drivers. Checking the plate before each rotation and at the close of each contract assigns the fine while the route sheet still exists.

The corridor to Chile through Agua Negra opens seasonally and concentrates document and cargo checks; a truck with open fines in the province sees them resurface at every later check. A monthly check per plate, with the per-source result stored, keeps traceability towards the client and the court.

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 guide describes. The API page details access.

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

Limits and considerations

  • Mining-route fines are ruled on in departments far from where the infraction occurred; the defence period runs from the notice.
  • 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