Skip to main content
The Solicitud API provides complete CRUD operations for transport solicitudes, including approval workflow, status history tracking, and email notifications.

​
Base Path

All Solicitud endpoints are prefixed with /solicitud.

​
Key Features

  • Request Creation: Create new transport solicitudes with multiple locations
  • Approval Workflow: Approve, reject, or cancel solicitudes
  • Status Management: Track status changes through complete history
  • Location Management: Manage multiple pickup/destination locations with return trips
  • Email Notifications: Automatic notifications to requesters and approvers
  • Advanced Filtering: Filter by status, department, priority, service type, dates, and more

​
Solicitud Lifecycle

  1. PENDIENTE_APROBACION - Initial state when created
  2. APROBADA - Approved by designated approver
  3. RECHAZADA - Rejected by approver (final state)
  4. CANCELADA - Cancelled by requester or approver (final state)
  5. COMPLETADA - All associated missions completed (final state)

​
Available Endpoints

Create Solicitud

Create a new transport solicitud

List Solicitudes

List solicitudes with pagination and filters

Get Solicitud

Retrieve a specific solicitud by ID

Update Solicitud

Update a pending solicitud

Approve Solicitud

Approve a pending solicitud

Reject Solicitud

Reject a pending solicitud

Cancel Solicitud

Cancel an active solicitud

Solicitud History

View status change history

Delete Solicitud

Soft delete a pending solicitud

​
Common Response Format

All endpoints return responses in the following format: 
{
  "success": true,
  "message": "Solicitud creada exitosamente",
  "data": {
    // Response data
  }
}

​
Error Handling

Error responses include:
  • 400 - Bad Request (validation errors)
  • 404 - Not Found (solicitud doesn’t exist)
  • 409 - Conflict (invalid state transition)
  • 422 - Unprocessable Entity (business logic validation)
  • 500 - Internal Server Error
Missions are not created automatically when a solicitud is approved. The approver must manually create missions in the Missions module.

Build docs developers (and LLMs) love

Get started for freeTalk to us