Skip to main content

Overview

The Vehicle Documents API provides comprehensive endpoints for managing all required vehicle documentation including:
  • SOAT (Mandatory Traffic Accident Insurance)
  • RTM (Technical-Mechanical Review)
  • Insurance Policies (Póliza de Seguro)
All endpoints support expiration tracking, automatic alerts, and dashboard analytics.

Base URL

/api/documentos

Authentication

All endpoints require JWT authentication. Include your token in the Authorization header:
Authorization: Bearer YOUR_JWT_TOKEN

Endpoints

Document Management

List Documents

Retrieve all vehicle documents with filtering and pagination

Create Document

Add new vehicle documentation records

Update Document

Update existing vehicle documents

Dashboard & Analytics

Dashboard

KPIs, expiration alerts, calendar events, and analytics

Document Types

The API manages three primary document types:
TypeDescriptionField Prefix
SOATMandatory Traffic Accident Insurancefecha_vencimiento_soat, pdf_soat
RTMTechnical-Mechanical Reviewfecha_vencimiento_rtm, pdf_rtm
PólizaInsurance Policyfecha_vencimiento_poliza, pdf_poliza

Document Status

Documents are automatically categorized based on days until expiration:
StatusDays RemainingColor
VENCIDO< 0Red
POR_VENCER0-30Orange
PROXIMO31-60Yellow
VIGENTE> 60Green
SIN_FECHANo dateSlate

Common Response Fields

id
integer
Unique document identifier
placa
string
Vehicle license plate number
area_operacion
string
Operating area or department
fecha_vencimiento_soat
string
SOAT expiration date (ISO 8601 format)
fecha_vencimiento_rtm
string
RTM expiration date (ISO 8601 format)
fecha_vencimiento_poliza
string
Insurance policy expiration date (ISO 8601 format)
pdf_soat
string
URL to SOAT PDF document
pdf_rtm
string
URL to RTM PDF document
pdf_poliza
string
URL to insurance policy PDF document

Error Handling

All endpoints return standard HTTP status codes:
  • 200 - Success
  • 201 - Created
  • 204 - No Content (for deletions)
  • 400 - Bad Request
  • 404 - Not Found
  • 500 - Internal Server Error
Error responses include a message:
{
  "error": "Error message description"
}

Build docs developers (and LLMs) love