Track Orders
This API allows the creation and immediate tracking of order fulfillment. If the route has been planned and exists in the HyperTrack system, then tracking can be initiated using the route_handle.
Request
- Base URLhttps://v3.api.hypertrack.com
- Auth
- HTTP basic
- or HTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Unique Handle of route to be tracked. if provided other parameters are not required and will be ignored if provided
One of device_id or driver handle is mandatory
One of device_id or worker handle is mandatory
Unique Handle of Ops Group for which orders are to be tracked
One of device_id or driver handle is mandatory
Tracking mode of the order. Note that on_time and flex are deprecated modes.
Route version.
[BETA] Worker phone number for closeout reconciliation. Only used when closeout_mode is 'standalone'.
Mode to control the active device for tracking orders. The following options are available:
- login : Order tracking is based on the device the worker last logged into. When the worker logs into a new device, the orders automatically transfer to the new device. This is the default setting.
- closest_to_destination : Order tracking is based on the device closest to the order's destination. The system monitors all of the worker's recent devices and selects the one nearest to the destination for tracking the order.
- manual : Order tracking remains on the device that was active when the order was created.
Response
Successful response
Unique identifier for the route
Current state of route
Value indicating the latest updated state of the route
Timestamp at which the route was created
Embeddable link that renders the route profile view
URL safe unique identifier for the ops group to which the orders in the route are associated
Value representing whether the order is tracked in on_shift, pre_shift or full_shift mode. Modes such as on_time and flex are deprecated.
Value indicating how the orders in the route were planned
Timestamp at which the route tracking started
Timestamp at which the route was assigned to a driver
Timestamp at which the orders were planned into this route
Timestamp at which the route was completed
Unique identifier for a device
Unique customer provided identifier for the driver
Unique customer provided identifier for the worker
Additional customer provided information about the route
Actual distance travelled by the driver to fulfill all orders in the route
Actual time spent by the driver to fulfill all orders in the route
Unique identifier for the plan to which the route belongs to
List of devices among which the route is expected to be tracked
Source of the route completion
Scheduled start time of the route
Indicates the ratio of time tracked to expected tracking time of route. Values lie between 0.0 and 1.0
Time in seconds to receive first event from device after order start
Time in seconds to receive first location from device after order start
Configuration to identify where routes are expected to end
Changes
No recorded changes to this operation across all 1 revision of this API.