Skip to main content
POST
/
api
/
verificacionesconductorcampana
curl -X POST https://api.example.com/api/verificacionesconductorcampana \
  -H "Content-Type: multipart/form-data" \
  -F "cedula_conductor=1234567890" \
  -F "id_campana=45" \
  -F "fecha_registro=2026-03-09" \
  -F "tipo_verificacion=inicial" \
  -F "imagen_evidencia=@/path/to/vehicle_photo.jpg" \
  -F "estado=1"
{
  "id_verificacion": 891,
  "cedula_conductor": 1234567890,
  "id_campana": 45,
  "fecha_registro": "2026-03-09",
  "tipo_verificacion": "inicial",
  "imagen_evidencia": "media/verification_45_1234567890_20260309_inicial.jpg",
  "estado": 1
}
This endpoint captures verification events throughout a campaign’s lifecycle, ensuring drivers maintain compliance with branding requirements and campaign terms. Each verification includes photographic evidence and is categorized by type.

Request Body

cedula_conductor
integer
required
Driver’s national ID number for identification
id_campana
integer
required
Campaign ID being verified
fecha_registro
string
required
Verification date in YYYY-MM-DD format
tipo_verificacion
string
required
Type of verification being performed:
  • inicial: Initial vehicle branding verification
  • periodica: Periodic compliance check
  • aleatorio: Random spot check
  • mantenimiento: Branding maintenance verification
  • final: Campaign completion verification
  • incidente: Incident or complaint investigation
imagen_evidencia
file
required
Photographic evidence of the verification
  • Uploaded to: media/ directory
  • Supported formats: JPG, PNG
  • Should clearly show vehicle branding status
  • Recommended minimum resolution: 1920x1080
estado
integer
required
Verification result status:
  • 0: Failed/Non-compliant
  • 1: Passed/Compliant
  • 2: Pending review
  • 3: Requires follow-up

Response

id_verificacion
integer
Unique identifier for the verification record
cedula_conductor
integer
Driver’s national ID number
id_campana
integer
Campaign ID verified
fecha_registro
string
Date of verification (YYYY-MM-DD)
tipo_verificacion
string
Type of verification performed
imagen_evidencia
string
URL path to the uploaded evidence photo
estado
integer
Verification result status
curl -X POST https://api.example.com/api/verificacionesconductorcampana \
  -H "Content-Type: multipart/form-data" \
  -F "cedula_conductor=1234567890" \
  -F "id_campana=45" \
  -F "fecha_registro=2026-03-09" \
  -F "tipo_verificacion=inicial" \
  -F "imagen_evidencia=@/path/to/vehicle_photo.jpg" \
  -F "estado=1"
{
  "id_verificacion": 891,
  "cedula_conductor": 1234567890,
  "id_campana": 45,
  "fecha_registro": "2026-03-09",
  "tipo_verificacion": "inicial",
  "imagen_evidencia": "media/verification_45_1234567890_20260309_inicial.jpg",
  "estado": 1
}

Verification Workflow

1. Initial Verification (inicial)

  • When: After vehicle branding is complete
  • Purpose: Confirm proper branding installation
  • Requirements:
    • All selected branding areas properly installed
    • Branding matches campaign specifications
    • No damage or defects
  • Evidence: Photos of all branded vehicle parts
  • Next Steps: Driver approved to start tracking routes

2. Periodic Verification (periodica)

  • When: Scheduled intervals (weekly/bi-weekly)
  • Purpose: Ensure ongoing branding compliance
  • Requirements:
    • Branding remains intact
    • No significant wear or damage
    • Vehicle maintains cleanliness standards
  • Evidence: Photos of vehicle exterior
  • Impact: Continued campaign participation

3. Random Spot Check (aleatorio)

  • When: Unannounced inspections
  • Purpose: Quality assurance and fraud prevention
  • Requirements:
    • Immediate verification upon request
    • Real-time photo submission
    • Location verification
  • Evidence: GPS-tagged photos
  • Consequences: Failed checks may suspend earnings

4. Maintenance Verification (mantenimiento)

  • When: After branding repair or replacement
  • Purpose: Confirm maintenance work completed
  • Requirements:
    • Damaged branding repaired/replaced
    • Matches original specifications
    • Professional installation quality
  • Evidence: Before/after photos
  • Result: Driver reinstated to active status

5. Final Verification (final)

  • When: Campaign end date
  • Purpose: Document branding removal and final state
  • Requirements:
    • Complete branding removal
    • No vehicle damage from removal
    • Final earnings calculation
  • Evidence: Photos of cleaned vehicle
  • Outcome: Campaign completion and payment release

6. Incident Verification (incidente)

  • When: After complaints or reported issues
  • Purpose: Investigate and document problems
  • Requirements:
    • Respond to specific complaint details
    • Provide evidence addressing concerns
    • May require immediate action
  • Evidence: Relevant photos/documentation
  • Resolution: Admin review determines outcome

Verification Types and Frequency

TypeFrequencyRequiredCritical
inicialOnce at startYesYes
periodicaWeekly/Bi-weeklyYesYes
aleatorioAs neededNoYes
mantenimientoAs neededWhen applicableYes
finalOnce at endYesYes
incidenteAs neededWhen reportedYes

Status Codes Impact

  • Status 0 (Failed):
    • Driver notified immediately
    • Route tracking may be suspended
    • Maintenance verification required
    • Earnings on hold until resolved
  • Status 1 (Passed):
    • Driver remains active
    • Earnings continue normally
    • Next verification scheduled
    • Good standing maintained
  • Status 2 (Pending):
    • Admin review required
    • Driver can continue routes
    • Decision expected within 48 hours
    • No immediate action required
  • Status 3 (Follow-up):
    • Minor issues identified
    • Driver given timeline to correct
    • Temporary status
    • Re-verification scheduled

Notes

  • Evidence photos must clearly show vehicle identification (plate number)
  • Photos should be taken in good lighting conditions
  • Multiple angles recommended for comprehensive verification
  • GPS metadata in photos helps prevent fraud
  • Failed verifications trigger automatic notifications
  • Verification history tracked for driver performance metrics
  • Three consecutive failed verifications may result in campaign removal
  • Evidence images stored for duration of campaign plus 90 days

Build docs developers (and LLMs) love