Fleet API

Authentication — Bearer token

Your 7Transfers contact issues a long-lived Bearer token for your fleet. Store it securely on your server and send it on every request as Authorization: Bearer {token}. There is no login step and no password for API access. If a token is lost or rotated, ask us for a new one.

Example request

curl -H 'Accept: application/json' \
     -H 'Authorization: Bearer 3757|Zj1EVDhKnrLAx0V1rsSmlzU2loolWKpS35A2qtRtc9e3d716' \
     'https://walatour.com/api/driver/bookings?status=assigned'

Sandbox — try the API

Use this public sandbox Bearer token to explore the Fleet API. It always has 20 demo bookings in status assigned (ref numbers FAPISB-01 and up). Accepting or cancelling them is fine — they are reset automatically every hour.

Sandbox Bearer token

3757|Zj1EVDhKnrLAx0V1rsSmlzU2loolWKpS35A2qtRtc9e3d716

Example request

curl -H 'Accept: application/json' \
     -H 'Authorization: Bearer 3757|Zj1EVDhKnrLAx0V1rsSmlzU2loolWKpS35A2qtRtc9e3d716' \
     'https://walatour.com/api/driver/bookings?status=assigned'

App login — not used by Fleet API integrations

This endpoint is only for the native driver/fleet mobile app (email, password and 2FA). Server integrations must ignore it and use the Bearer token above.

List bookings assigned to the fleet

Query parameters optional

Example

https://walatour.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"
}

• status_notes is required when status is rejected.
• Statuses onroute, arrived, onboard, noshow, completed require a recent driver GPS location (within 5 minutes). Send lat and lng in this same request, or share the location from the driver app. For office-side integration without GPS, use accepted, rejected, or canceled.

Driver location optional

{
  "status": "arrived",
  "lat": -34.8150,
  "lng": -58.5348,
  "accuracy": 12,
  "heading": 270,
  "speed": 0
}

• lat, lng — Latitude and longitude in decimal degrees. Send both or neither.
• accuracy — GPS accuracy in meters (optional)
• heading — Direction of travel in degrees, 0 to 360 (optional)
• speed — Speed in meters per second (optional)

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

Send driver_id, or a driver object when your drivers live in your own system. commission and fleet_commission are optional.

{
  "driver_id": 55,
  "commission": 10.00,
  "fleet_commission": 5.00,
  "driver_name": "Juan Perez",
  "driver_phone": "+905551112233",
  "vehicle_make": "Mercedes-Benz",
  "vehicle_model": "Vito",
  "vehicle_license_plate": "34 ABC 123"
}

Driver and vehicle optional

• driver_name — Driver full name
• driver_phone — Driver phone number
• vehicle_make — Vehicle make
• vehicle_model — Vehicle model
• vehicle_license_plate — Vehicle license plate

Drivers from your own system

{
  "commission": 10.00,
  "fleet_commission": 5.00,
  "driver": {
    "first_name": "Juan",
    "last_name": "Perez",
    "mobile_no": "+5491155551234",
    "vehicle_make": "Mercedes-Benz",
    "vehicle_model": "Vito",
    "vehicle_year": 2022,
    "vehicle_color": "black",
    "vehicle_license_plate": "AB 123 CD",
    "country": "AR",
    "city": "Buenos Aires"
  }
}

Required fields:

• driver.first_name — Driver first name
• driver.last_name — Driver last name
• driver.mobile_no — Driver mobile number, with country code. We use it to recognize the same driver on later bookings.
• driver.vehicle_make — Vehicle make
• driver.vehicle_model — Vehicle model
• driver.vehicle_year — Vehicle year (4 digits)
• driver.vehicle_color — Vehicle color, one of: white, black, silver, gray, blue, red, green, beige, brown, gold, orange, yellow, navy, burgundy
• driver.vehicle_license_plate — Vehicle license plate

Optional fields:

• driver.telephone_no, driver.address, driver.city, driver.postcode, driver.country

Response

{
  "success": true,
  "message": "Driver assigned.",
  "data": {
    "id": 9876,
    "driver_id": 55,
    "driver_name": "Juan Perez",
    "driver_phone": "+905551112233",
    "vehicle_make": "Mercedes-Benz",
    "vehicle_model": "Vito",
    "vehicle_license_plate": "34 ABC 123",
    "commission": 10.00,
    "fleet_commission": 5.00
  }
}

Logout

Revokes the current Bearer token. Service tokens issued by 7Transfers should not be logged out in normal operation; ask us to revoke a token if you need to rotate credentials.

Error format

All errors return JSON with a human-readable message.

{ "success": false, "message": "Human-readable message" }