Getting started
Include these headers on every request after login:
Accept: application/json
Content-Type: application/json
Authorization: Bearer {token}
Login — get token
Authenticate with fleet credentials to receive a Bearer token for subsequent requests.
Request
{
"email": "fleet@example.com",
"password": "your-password"
}
Response 200
{
"success": true,
"token": "1|xxxxxxxxxxxxxxxxxxxx",
"user": {
"id": 123,
"name": "Malaga Fleet",
"email": "fleet@example.com",
"is_driver": false,
"is_fleet": true
}
}
List bookings assigned to the fleet
Query parameters optional
statusall or assigned, accepted, onroute, arrived, onboard, completed, canceled, noshow, rejected, market
from_dateYYYY-MM-DD
to_dateYYYY-MM-DD
per_page1–100 (default 20)
Example
https://7transfers.com/api/driver/bookings?status=assigned&from_date=2026-04-11&per_page=50
Response 200
{
"success": true,
"data": [
{
"id": 9876,
"ref_number": "T2S-12345",
"status": "assigned",
"status_label": "Assigned",
"date": "2026-04-15 10:30:00",
"from_address": "Malaga Airport (AGP)",
"to_address": "Hotel Marbella Club",
"passengers": 3,
"vehicle_list": "Business Van",
"luggage": 4,
"hand_luggage": 3,
"assigned_driver": null,
"commission": 0,
"flight_number": "FR1234",
"meet_and_greet": true,
"coordinate_start_lat": 36.6749,
"coordinate_start_lon": -4.4991,
"coordinate_end_lat": 36.5098,
"coordinate_end_lon": -4.8826
}
],
"meta": {
"current_page": 1,
"last_page": 3,
"per_page": 20,
"total": 47
}
}
Booking details
Returns the full booking: passenger, contact, addresses, coordinates, status history, action buttons, extras (child seats, wheelchair, waiting time, etc.) and attached files.
Update booking status
Request
{
"status": "accepted",
"status_notes": "Optional note"
}
Valid status values:
accepted, rejected, onroute, arrived, onboard, noshow, completed, canceled
status_notes is required when status is rejected.
- Statuses
onroute, arrived, onboard, noshow, completed require a recent driver GPS location (within 5 minutes). For office-side integration, use accepted, rejected, or canceled.
Response 200
{
"success": true,
"data": { "id": 9876, "status": "accepted" }
}
List fleet's own drivers
Response
{
"success": true,
"data": [
{ "id": 55, "name": "Juan Perez", "email": "juan@example.com" }
]
}
Assign a driver to a booking
Request
{
"driver_id": 55,
"commission": 10.00,
"fleet_commission": 5.00
}
Response
{
"success": true,
"message": "Driver assigned.",
"data": {
"id": 9876,
"driver_id": 55,
"driver_name": "Juan Perez",
"commission": 10.00,
"fleet_commission": 5.00
}
}
Logout
Revokes the current Bearer token.
Error format
All errors return JSON with a human-readable message.
{ "success": false, "message": "Human-readable message" }
401 Invalid credentials or token
403 Not a fleet user / booking not owned by fleet
404 Booking not found
422 Validation error or invalid state transition