Required. Must be in the format providers/{provider}/trips/{trip}. The provider must be the Project ID (for example, sample-consumer-project) of the Google Cloud Project of which the service account making this call is a member.
Required. The Trip associated with the update. The following fields are maintained by the Fleet Engine. Do not update them using Trip.update. * * current_route_segment * * current_route_segment_end_point * * current_route_segment_traffic * * current_route_segment_traffic_version * * current_route_segment_version * * dropoff_time * * eta_to_next_waypoint * * intermediate_destinations_version * * last_location * * name * * number_of_passengers * * pickup_time * * remaining_distance_meters * * remaining_time_to_first_waypoint * * remaining_waypoints * * remaining_waypoints_version * * route When you update the Trip.vehicle_id for a shared trip, you must supply the list of Trip.vehicle_waypoints to specify the order of the remaining waypoints, otherwise the order will be undetermined. When you specify Trip.vehicle_waypoints, the list must contain all the remaining waypoints of the vehicle's trips, with no extra waypoints. You must order these waypoints such that for a given trip, the pickup point is before intermediate destinations, and all intermediate destinations come before the drop-off point. An EXCLUSIVE trip's waypoints must not interleave with any other trips. The trip_id, waypoint_type and location fields are used, and all other TripWaypoint fields in vehicle_waypoints are ignored. To avoid a race condition for trips with multiple destinations, you should provide Trip.intermediate_destinations_version when updating the trip status to ENROUTE_TO_INTERMEDIATE_DESTINATION. The Trip.intermediate_destinations_version passed must be consistent with Fleet Engine's version. If it isn't, the request fails.
Required. Must be in the format
providers/{provider}/trips/{trip}. The provider must
be the Project ID (for example, sample-consumer-project) of the Google
Cloud Project of which the service account making this call is a member.
Returns
Type
Description
string
setName
Required. Must be in the format
providers/{provider}/trips/{trip}. The provider must
be the Project ID (for example, sample-consumer-project) of the Google
Cloud Project of which the service account making this call is a member.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getTrip
Required. The Trip associated with the update.
The following fields are maintained by the Fleet Engine. Do not update
them using Trip.update.
current_route_segment
current_route_segment_end_point
current_route_segment_traffic
current_route_segment_traffic_version
current_route_segment_version
dropoff_time
eta_to_next_waypoint
intermediate_destinations_version
last_location
name
number_of_passengers
pickup_time
remaining_distance_meters
remaining_time_to_first_waypoint
remaining_waypoints
remaining_waypoints_version
route
When you update the Trip.vehicle_id for a shared trip, you must supply
the list of Trip.vehicle_waypoints to specify the order of the remaining
waypoints, otherwise the order will be undetermined.
When you specify Trip.vehicle_waypoints, the list must contain all
the remaining waypoints of the vehicle's trips, with no extra waypoints.
You must order these waypoints such that for a given trip, the pickup
point is before intermediate destinations, and all intermediate
destinations come before the drop-off point. An EXCLUSIVE trip's
waypoints must not interleave with any other trips.
The trip_id, waypoint_type and location fields are used, and all
other TripWaypoint fields in vehicle_waypoints are ignored.
To avoid a race condition for trips with multiple destinations, you
should provide Trip.intermediate_destinations_version when updating
the trip status to ENROUTE_TO_INTERMEDIATE_DESTINATION. The
Trip.intermediate_destinations_version passed must be consistent with
Fleet Engine's version. If it isn't, the request fails.
The following fields are maintained by the Fleet Engine. Do not update
them using Trip.update.
current_route_segment
current_route_segment_end_point
current_route_segment_traffic
current_route_segment_traffic_version
current_route_segment_version
dropoff_time
eta_to_next_waypoint
intermediate_destinations_version
last_location
name
number_of_passengers
pickup_time
remaining_distance_meters
remaining_time_to_first_waypoint
remaining_waypoints
remaining_waypoints_version
route
When you update the Trip.vehicle_id for a shared trip, you must supply
the list of Trip.vehicle_waypoints to specify the order of the remaining
waypoints, otherwise the order will be undetermined.
When you specify Trip.vehicle_waypoints, the list must contain all
the remaining waypoints of the vehicle's trips, with no extra waypoints.
You must order these waypoints such that for a given trip, the pickup
point is before intermediate destinations, and all intermediate
destinations come before the drop-off point. An EXCLUSIVE trip's
waypoints must not interleave with any other trips.
The trip_id, waypoint_type and location fields are used, and all
other TripWaypoint fields in vehicle_waypoints are ignored.
To avoid a race condition for trips with multiple destinations, you
should provide Trip.intermediate_destinations_version when updating
the trip status to ENROUTE_TO_INTERMEDIATE_DESTINATION. The
Trip.intermediate_destinations_version passed must be consistent with
Fleet Engine's version. If it isn't, the request fails.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Google Maps FleetEngine V1 Client - Class UpdateTripRequest (0.4.1)\n\nVersion latestkeyboard_arrow_down\n\n- [0.4.1 (latest)](/php/docs/reference/maps-fleetengine/latest/V1.UpdateTripRequest)\n- [0.4.0](/php/docs/reference/maps-fleetengine/0.4.0/V1.UpdateTripRequest)\n- [0.3.1](/php/docs/reference/maps-fleetengine/0.3.1/V1.UpdateTripRequest)\n- [0.2.0](/php/docs/reference/maps-fleetengine/0.2.0/V1.UpdateTripRequest)\n- [0.1.6](/php/docs/reference/maps-fleetengine/0.1.6/V1.UpdateTripRequest) \nReference documentation and code samples for the Google Maps FleetEngine V1 Client class UpdateTripRequest.\n\nUpdateTrip request message.\n\nGenerated from protobuf message `maps.fleetengine.v1.UpdateTripRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Maps \\\\ FleetEngine \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getHeader\n\nThe standard Fleet Engine request header.\n\n### hasHeader\n\n### clearHeader\n\n### setHeader\n\nThe standard Fleet Engine request header.\n\n### getName\n\nRequired. Must be in the format\n`providers/{provider}/trips/{trip}`. The provider must\nbe the Project ID (for example, `sample-consumer-project`) of the Google\nCloud Project of which the service account making this call is a member.\n\n### setName\n\nRequired. Must be in the format\n`providers/{provider}/trips/{trip}`. The provider must\nbe the Project ID (for example, `sample-consumer-project`) of the Google\nCloud Project of which the service account making this call is a member.\n\n### getTrip\n\nRequired. The Trip associated with the update.\n\nThe following fields are maintained by the Fleet Engine. Do not update\nthem using Trip.update.\n\n- `current_route_segment`\n- `current_route_segment_end_point`\n- `current_route_segment_traffic`\n- `current_route_segment_traffic_version`\n- `current_route_segment_version`\n- `dropoff_time`\n- `eta_to_next_waypoint`\n- `intermediate_destinations_version`\n- `last_location`\n- `name`\n- `number_of_passengers`\n- `pickup_time`\n- `remaining_distance_meters`\n- `remaining_time_to_first_waypoint`\n- `remaining_waypoints`\n- `remaining_waypoints_version`\n- `route` When you update the `Trip.vehicle_id` for a shared trip, you must supply the list of `Trip.vehicle_waypoints` to specify the order of the remaining waypoints, otherwise the order will be undetermined. When you specify `Trip.vehicle_waypoints`, the list must contain all the remaining waypoints of the vehicle's trips, with no extra waypoints. You must order these waypoints such that for a given trip, the pickup point is before intermediate destinations, and all intermediate destinations come before the drop-off point. An `EXCLUSIVE` trip's waypoints must not interleave with any other trips. The `trip_id`, `waypoint_type` and `location` fields are used, and all other TripWaypoint fields in `vehicle_waypoints` are ignored. To avoid a race condition for trips with multiple destinations, you should provide `Trip.intermediate_destinations_version` when updating the trip status to `ENROUTE_TO_INTERMEDIATE_DESTINATION`. The `Trip.intermediate_destinations_version` passed must be consistent with Fleet Engine's version. If it isn't, the request fails.\n\n### hasTrip\n\n### clearTrip\n\n### setTrip\n\nRequired. The Trip associated with the update.\n\nThe following fields are maintained by the Fleet Engine. Do not update\nthem using Trip.update.\n\n- `current_route_segment`\n- `current_route_segment_end_point`\n- `current_route_segment_traffic`\n- `current_route_segment_traffic_version`\n- `current_route_segment_version`\n- `dropoff_time`\n- `eta_to_next_waypoint`\n- `intermediate_destinations_version`\n- `last_location`\n- `name`\n- `number_of_passengers`\n- `pickup_time`\n- `remaining_distance_meters`\n- `remaining_time_to_first_waypoint`\n- `remaining_waypoints`\n- `remaining_waypoints_version`\n- `route` When you update the `Trip.vehicle_id` for a shared trip, you must supply the list of `Trip.vehicle_waypoints` to specify the order of the remaining waypoints, otherwise the order will be undetermined. When you specify `Trip.vehicle_waypoints`, the list must contain all the remaining waypoints of the vehicle's trips, with no extra waypoints. You must order these waypoints such that for a given trip, the pickup point is before intermediate destinations, and all intermediate destinations come before the drop-off point. An `EXCLUSIVE` trip's waypoints must not interleave with any other trips. The `trip_id`, `waypoint_type` and `location` fields are used, and all other TripWaypoint fields in `vehicle_waypoints` are ignored. To avoid a race condition for trips with multiple destinations, you should provide `Trip.intermediate_destinations_version` when updating the trip status to `ENROUTE_TO_INTERMEDIATE_DESTINATION`. The `Trip.intermediate_destinations_version` passed must be consistent with Fleet Engine's version. If it isn't, the request fails.\n\n### getUpdateMask\n\nRequired. The field mask indicating which fields in Trip to update.\n\nThe `update_mask` must contain at least one field.\n\n### hasUpdateMask\n\n### clearUpdateMask\n\n### setUpdateMask\n\nRequired. The field mask indicating which fields in Trip to update.\n\nThe `update_mask` must contain at least one field."]]
