Introduction

What is the Nexcar API?#

Nexcar processes vehicle cases end-to-end: you send us documents (invoice, owner ID, vehicle tax payment receipt, REPUVE certificate, proof of address, etc.) and we apply OCR, automatic classification and business rules so your team or your system gets structured, decision-ready data back.

The API is built for integrations with:

• Insurers receiving claims that need documentary validation of the affected vehicle.
• Used-car marketplaces that need fast document verification before a sale.
• Auto-loan originators that must validate the legal owner.
• Compliance teams that need an audit trail for every document.

Key concepts#

• Case (case): the logical container for a vehicle. Each case has a case_id (UUID) and groups every document belonging to that vehicle.
• Document (document): an individual file (PDF, image, XML) attached to a case. Each one is identified by a document_id.
• Document type: the file's category (invoice, ID, REPUVE, tax, etc.). It can be set manually on upload or detected automatically.
• Webhook: an HTTP notification we send to your server when a document or case changes state (upload completed, OCR ready, validation finished).

Typical integration flow#

1. Create a case with POST /v1/cases. You get a case_id.
2. Attach documents to the case with POST /v1/documents, one per file. Each call returns a document_id.
3. Receive webhooks as processing progresses: classification, OCR, data extraction.
4. Read results with GET /v1/documents/{id} or GET /v1/cases/{id} whenever you need them.

Environments#

Support#

Ready to integrate? Continue with Authentication or email us at support@nexcar.mx.