Skip to main content

Ground Transport

Many disruptions need more than a room — passengers have to get from the airport to the hotel and back. Nexa's transport module plans, assigns, and tracks ground transport alongside the hotel booking.

How it works​

  • Transport segments are attached to a reservation (or a group of reservations for shared shuttles).
  • Segments have a direction (AIRPORT_TO_HOTEL, HOTEL_TO_AIRPORT), a scheduled time, and a vehicle capacity.
  • Nexa batches groups with compatible timings and same-hotel destinations onto shared shuttles; high-tier passengers default to private cars per policy.
  • The transport provider can be a limited sandbox fleet, a third-party (a taxi/shuttle service), or manual assignments entered by the operator.

Transport policy​

{
  "transport": {
    "mode": "SHUTTLE",
    "perTier": {
      "BUSINESS": "PRIVATE_CAR",
      "FIRST":    "PRIVATE_CAR",
      "CREW":     "SHUTTLE",
      "ECONOMY":  "SHUTTLE"
    },
    "minutesBeforePickup": 45,
    "shuttleCapacity": 24
  }
}
  • mode — default mode when per-tier isn't specified.
  • perTier — override per tier.
  • minutesBeforePickup — how early to fetch passengers for their next flight.
  • shuttleCapacity — cap per shared vehicle; additional passengers roll onto another shuttle.

Creating segments​

Most segments are created automatically when a reservation confirms. To add one manually (e.g., a medical passenger needs a wheelchair van):

curl -X POST https://us-central1.api.nexastudio.io/transport/segments \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "reservationUrn": "urn:nexa:reservation:abc",
    "direction": "AIRPORT_TO_HOTEL",
    "scheduledAt": "2026-04-22T20:00:00Z",
    "vehicleType": "WHEELCHAIR_VAN",
    "specialRequirements": ["wheelchair", "companion"]
  }'

Shuttle consolidation​

The allocator prefers to cluster hotels so shuttle runs are efficient. When two groups land at the same hotel with compatible pickup windows, they share a shuttle automatically. When they don't:

  • A new shuttle is scheduled.
  • The capacity policy decides whether to wait-and-batch or dispatch early.

Vouchers​

When transport is present, the voucher email adds:

  • Pickup location (terminal / curb / meeting point)
  • Scheduled pickup time
  • Vehicle / driver identifier (when provided by the transport provider)
  • Contact number for the shuttle dispatcher

For the return leg (hotel → airport), a separate email goes out ~12 hours before the reaccommodated flight with the pickup time.

Operator actions​

  • Re-time a segment when the flight shifts: POST /transport/segments/:urn/retime.
  • Reassign vehicle when capacity changes: POST /transport/segments/:urn/vehicle.
  • Cancel a segment (e.g., passenger decided to take their own taxi): POST /transport/segments/:urn/cancel.

All actions require a reason and are audit-logged.

Was this helpful?