Endpoint
Authentication
Bearer token for authentication. Format:
Bearer <access_token>Description
This endpoint retrieves all vehicle-related catalog data in a single request. The catalogs are used to populate dropdown menus and provide reference data when creating or updating vehicle records. All catalogs are fetched in parallel for optimal performance.Response
Returns an object containing five catalog arrays.Array of vehicle brand objects from the
cat_marca tableArray of vehicle type objects from the
cat_tipo_vehiculo tableArray of vehicle class objects from the
cat_clase_vehiculo tableArray of fuel type objects from the
cat_combustible tableArray of compactor brand objects from the
cat_marca_compactadora tableResponse Example
Examples
Get all catalogs
Using in a Form
The catalog data is typically used to populate dropdown menus in vehicle forms:Error Responses
401 Unauthorized
500 Internal Server Error
Performance
- All five catalog queries are executed in parallel using
Promise.all()for optimal performance - Typical response time is under 200ms
- The catalogs are relatively static and can be cached on the client side
- Consider implementing client-side caching with a reasonable TTL (e.g., 1 hour) to reduce API calls
Catalog Relationships
These catalogs are used in thevehiculo_caracteristicas table:
marcas→vehiculo_caracteristicas.marca_idtipos→vehiculo_caracteristicas.tipo_vehiculo_idclases→vehiculo_caracteristicas.clase_vehiculo_idcombustibles→vehiculo_caracteristicas.combustible_idmarcasCompactadora→vehiculo_caracteristicas.marca_compactadora_id
Notes
- All catalogs return complete datasets (no pagination required)
- The
marcasCompactadoracatalog is only relevant for vehicles with class “Compactadora” - Catalog data is maintained separately and should be managed through administrative interfaces
- The response includes all fields from the catalog tables (typically just
idandnombre) - Empty arrays will be returned if a catalog table has no records