Skip to main content
Release Date: August 2026 · Product: GNet Platform · Endpoint: POST /Platform.svc/sendTrip · View API Docs

New Field

luggageCount has been added in two places on the reservation payload.

1. luggageCount on the reservation string · optional

The number of pieces of luggage for the trip. Send it alongside passengerCount so the receiving operator can assign a vehicle with enough capacity.
Usage guidance:
Include luggageCount in the payload when known. Partners that cannot store the value natively receive it appended to the trip notes as Luggage Count : <value>, so it still reaches the driver.
Read luggageCount from the inbound payload and map it to your own luggage or baggage field. Treat a missing or empty value as “not specified” rather than zero.

2. luggageCount on quote vehicle options string · optional

On a QUOTE reservation, each entry in the fees array represents an available vehicle option. Those entries now carry the vehicle’s capacity and display details. JSON example:
On a reservation request, luggageCount is how much luggage the passenger has. On a quote option, it is how much luggage the vehicle holds.

Backward Compatibility

The field is optional everywhere it appears. Existing integrations require no changes. If your platform does not send luggageCount, trip processing is unaffected.

Questions?

Contact the GNet Platform team at support@grdd.net.