Patentes Chile avatar

Patentes Chile

Pricing

from $0.49 / 1,000 results

Go to Apify Store
Patentes Chile

Patentes Chile

Chilean vehicle & license plate lookup by plate number. Get owner (RUT, name), vehicle details, SOAP, itemized traffic fines (ROL/CAUSA, year, commune), technical inspection & restrictions in one JSON dataset. Cross-referenced data for moto and vehiculo. Ready for APIs, Make, Zapier.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

DataCach

DataCach

Maintained by Community

Actor stats

0

Bookmarked

23

Total users

4

Monthly active users

2 days ago

Last modified

Share

🇨🇱 Patentes Chile By Vehicle Type – Vehicle & License Plate Lookup

API de consultas de patentes chilenas. This actor exposes a Chilean vehicle lookup API: search by plate (moto/vehiculo), by RUT (returns every vehicle the owner has), or by VIN (chassis number), and get owner, vehicle, SOAP, detailed traffic fines (ROL/CAUSA, year, commune), technical inspection, and restrictions in structured JSON—ready to call from your app, export to CSV/Excel, or plug into Make, Zapier, or any REST client.

Keywords: API patentes Chile, consulta patentes Chile, API consulta patente, buscar patente Chile, datos vehículo Chile, multas por patente, SOAP vehículo Chile, ROL CAUSA multas, lookup patente Chile, API vehículos Chile.


Get Chilean vehicle and license plate (patente) data in one place.
Search by plate, by RUT (returns all the owner's vehicles), or by VIN, and receive owner details, vehicle info, SOAP insurance status, detailed traffic fines, technical inspection, and restrictions—delivered as clean JSON for your apps, spreadsheets, or integrations.


🎯 Detailed traffic fines (multas) – cross-referenced data, real added value

This actor doesn’t just tell you whether a plate has fines. It cross-references the main vehicle report with the fines database and returns a full itemized list for each plate:

  • multas_items – one entry per fine: ROL/CAUSA (case ID), year, and commune (e.g. JPL Vitacura, Renca, Maipú). Use it to validate with the municipality, prioritize payment, or audit history.
  • multas_description – summary text from the source (e.g. total count, recommendation to validate with Registro Civil).

You get vehicle + owner + per-fine breakdown in a single run, without switching tools or manually merging data.


✨ What can you get?

  • Three search modes → by plate (moto/vehiculo), by RUT (returns every vehicle the owner has and looks up each one), or by VIN (chassis number → that vehicle's full report).
  • Per vehicle → owner (RUT + name), vehicle type (car or motorcycle), brand, model, year, color, engine and chassis numbers.
  • SOAP (Seguro Obligatorio) → status, insurer, start and expiry dates.
  • Traffic fines (detailed) → full list of fines with ROL/CAUSA, year, and commune per item, plus summary description.
  • Technical inspection & emissions → revision due month and gas-related data.
  • Vehicle restrictions → e.g. Santiago area restrictions.
  • Every record stamped with extraction date & time (UTC) for auditing.

🔍 Typical use cases

  1. Used car checks – verify vehicle data and owner before buying or selling; get the full list of fines (ROL/CAUSA, commune) to validate with the municipality.
  2. Fleet management – keep SOAP and technical inspection dates in one dataset; track which plates have fines and where (commune/JPL).
  3. Insurance & risk – confirm SOAP status and check for fines or restrictions using itemized multas data.
  4. Lead enrichment – add vehicle and owner details to customer or lead lists.
  5. Compliance & audits – export structured data for reporting or internal checks; use multas_items to cross-check ROL/CAUSA with municipal records.

🆚 Why use this actor?

  • Cross-referenced multas data – vehicle info and a per-fine list (ROL/CAUSA, year, commune) in one dataset; no manual merging.
  • Three search modes – by plate (moto/vehiculo), by RUT (all the owner's vehicles), or by VIN, in a single tool.
  • Structured output – JSON ready for databases, CRMs, Make, Zapier, or your API.
  • Multiple terms per run – look up to 30 plates/RUTs/VINs in one execution (paid plans).

📥 Input

FieldTypeRequiredDescription
search_termsarrayTerms to look up, matching search_type: plates, RUTs, or VINs (e.g. ["BBCC11"], ["13008100-2"], ["1GCDT13E878215126"]). Free: 1 term per run; paid: up to 30.
search_typestring"moto", "vehiculo", "rut", or "vin". Default: "moto". With "rut", the actor returns every vehicle the owner has and looks up each one (each vehicle is one dataset item). With "vin", it looks up the vehicle by its chassis number.

Examples

By plate:

{
"search_type": "vehiculo",
"search_terms": ["ABCD12", "HSH020"]
}

By RUT (expands to all the owner's vehicles):

{
"search_type": "rut",
"search_terms": ["13008100-2"]
}

By VIN (chassis number):

{
"search_type": "vin",
"search_terms": ["1GCDT13E878215126"]
}

📤 Output

Each dataset item is one plate result. Field names follow the source (Spanish).

{
"input": {
"search_term": "PG414",
"search_type": "moto"
},
"extraction_date": "05-03-2026",
"extraction_datetime": "2026-03-05T04:25:38.340161+00:00",
"revision_tecnica": {
"mes_de_revision": "JULIO"
},
"gases": {},
"propietario": {
"rut": "17753447-1",
"nombre": "PABLO IGNACIO ARROYO INOSTROZA"
},
"patente": "PG0414-0",
"tipo": "MOTO",
"marca": "VERONA",
"modelo": "VERONA 50 150 CC",
"ano": "2007",
"color": "ROJO",
"n_motor": "1P57QMJ060610367",
"n_chasis": "LZBTX630161002770",
"procedencia": "CHINA",
"fabricante": "VERONA",
"multas": {
"multas_description": "La patente PG0414 posee 31 multas , te recomendamos validarlo con un Certificado de Multas de Registro Civil. INFORME DE MULTAS",
"multas_items": [
{
"rol_causa": "Z652004",
"ano": "2018",
"comuna": "1 JPL VITACURA"
},
{
"rol_causa": "0030530001",
"ano": "2021",
"comuna": "PEÑALOLEN JPL"
},
{
"rol_causa": "T179570",
"ano": "2022",
"comuna": "RENCA JPL"
},
{
"rol_causa": "1129432",
"ano": "2022",
"comuna": "CERRILLOS JPL"
},
{
"rol_causa": "Z387189",
"ano": "2022",
"comuna": "2 JPL MAIPU"
},
{
"rol_causa": "Z400422",
"ano": "2023",
"comuna": "1 JPL MAIPU"
},
{
"rol_causa": "W449047",
"ano": "2023",
"comuna": "4 JPL SANTIAGO"
},
{
"rol_causa": "T28038",
"ano": "2023",
"comuna": "2 JPL PUDAHUEL"
},
{
"rol_causa": "T126006",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T124025",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T120369",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T142341",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T140991",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T140548",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T138915",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T151114",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "Z48941",
"ano": "2024",
"comuna": "1 JPL PUDAHUEL"
},
{
"rol_causa": "T165132",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T167466",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T171760",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T175203",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T170396",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T191631",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T192228",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "Y860127",
"ano": "2024",
"comuna": "2 JPL SANTIAGO"
},
{
"rol_causa": "T230634",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "Y166832",
"ano": "2024",
"comuna": "2 JPL SANTIAGO"
},
{
"rol_causa": "T232652",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T234887",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "T357649",
"ano": "2024",
"comuna": "RENCA JPL"
},
{
"rol_causa": "Z433176",
"ano": "2023",
"comuna": "1 JPL MAIPU"
}
]
},
"transporte_transporte_publico": "NO",
"transporte_tipo_transporte_publico": "NO APLICA",
"restriccion_vehicular": {
"condicion": "SI, TODOS LOS VIERNES DE MAYO HASTA 31 DE AGOSTO 2025, DESDE 7:30 A 21:00 HRS (EXCEPTO FESTIVOS)",
"comunas_de_puente_alto_y_san_bernardo": "APLICA",
"provincia_de_santiago": "APLICA"
}
}

In the Apify run, use the Overview view to see results in a table.

RUT mode: each of the owner's vehicles is a separate dataset item with the same structure, plus source_rut and source_owner so you can trace which RUT/owner it came from. VIN mode: one item; the plate appears in the patente field and the searched VIN in n_chasis.

🚀 How to run

From Apify Console

  1. Open the Actor and click Run.
  2. Enter input (e.g. paste the JSON above).
  3. Check the Dataset tab for results; use Overview for a table view.

From code

from apify_client import ApifyClient
client = ApifyClient("<APIFY_API_TOKEN>")
run = client.actor("username~patentes-chile").call({
"search_type": "vehiculo",
"search_terms": ["ABCD12", "HSH020"]
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

With cURL

curl -X POST \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <APIFY_API_TOKEN>' \
-d '{"search_type":"moto","search_terms":["HSH020"]}' \
https://api.apify.com/v2/acts/username~patentes-chile/runs?waitForFinish=1

💰 Pricing & limits

FreePaid
Terms per run (plates / RUTs / VINs)1Up to 30
Vehicles per RUT (RUT mode)1All of the owner's vehicles
OutputSame JSON structureSame JSON structure

On a free account, a RUT search returns only the first vehicle of that owner; upgrade to a paid plan to get every vehicle the RUT has. Billing is based on your Apify plan and this Actor’s configuration. See Apify pricing.

💬 Support & feedback

Need help or have a feature request?
Open an issue on the Actor’s page on Apify—we’ll get back to you as soon as we can.