Catalog of types you can assign when uploading a document. If you omit the type, Nexcar tries to detect it automatically.
Type (type) | Description | Typical extracted data |
|---|---|---|
factura | Invoice (PDF) or CFDI XML for the vehicle | VIN, issuer/recipient RFC, total amount, date |
factura_xml | CFDI 4.0 XML | UUID, RFC, totals, line items |
ine | Mexican INE/IFE official ID of the owner | Name, CURP, validity, voter key |
pasaporte | Mexican or foreign passport | Name, date of birth, validity |
repuve | REPUVE certificate | VIN, make, model, year, vehicle status |
tenencia | State vehicle-tax payment receipt | Year, amount, payment date, plate |
placas | Circulation card or plates certificate | Plate, validity, owner |
comprobante_domicilio | Utility bill (electricity, water, phone, property) | Address, holder, issue date |
comprobante_pago | Bank receipt / SPEI | Amount, bank, date, beneficiary |
pedimento | Customs declaration (imported vehicles) | Pedimento number, customs office, date |
verificacion | Vehicle emissions inspection certificate | Hologram, validity, plate |
multas | Traffic violations clearance | Outstanding fines, issue date |
acta_nacimiento | Owner's birth certificate | Name, CURP, date and place |
comprobante_ingresos | Bank statement or pay stub | Holder, period, amount |
responsiva | Signed transfer-of-responsibility letter | Buyer, seller, date, VIN |
type, Nexcar respects your classification but may flag inconsistencies.type, automatic content-based classification runs. The result arrives via the document.classified webhook.POST /v1/documents/{id}/classify or /reclassify (the latter re-runs OCR).Some types accept a parent document through parent_file_id. For instance:
factura_xml can be linked to its matching factura (PDF).comprobante_pago can be linked to the tenencia it pays for.This way, lookups return coherent groups of related documents.