/api/p/v{version}/visibility/inbound/{loadNumber}/history

The location history endpoint provides access to inbound updates for a specific load by using the loadNumber and version in your request. The history includes location updates from various sources, such as ELD integrations (if enabled for assets), manual Checkcalls, EDI & Visibility integrations, or updates from the driver app. These updates help track the load's location, detailing event types, timestamps, and asset information. For guidance on versioning and how to include it in your requests, visit the Versioning page.

Request Parameters

The following parameters are required in the URL:

Parameter	Type	Required	Description
version	String	Yes	The API version you are using (e.g., "v1").
loadNumber	String	Yes	The unique number assigned to the load for tracking purposes.

Example CURL Request

curl --location 'https://integrations.alvys.com/api/p/v1/visibility/inbound/12345/history' \
--header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Replace YOUR_ACCESS_TOKEN with your actual Bearer token and 12345 with the load number you wish to track.

Response Fields

The following fields are included in the response:

Field	Type	Description
id	String	The unique identifier of the location update.
externalId	String	The external ID related to the update.
tripNumber	String	The trip number linked to the load.
loadNumber	String	The load number for which the update is recorded.
eventType	String	The type of event, typically "Location".
sharedAt	String (Date-Time)	The date and time when the update was shared.
destination	String	The destination of the load.
truckNumber	String	The number of the truck transporting the load.
driverName	String	The name of the driver.
trailerNumber	String	The number of the trailer being used.
stopId	String	The ID of the stop associated with the location update.
locationId	String	The ID of the location where the update occurred.
sharedBy	String	The entity (user or system) that shared the update.
reason	String	The reason for the update, if provided. There is defined list on system, depending on integration. E.g.: "NA"- Normal Appointment.
address	Object	The address details of the location update.
address.street	String	The street of the location.
address.city	String	The city of the location.
address.state	String	The state of the location.
address.zipCode	String	The postal code of the location.
coordinates	Object	The geographic coordinates of the location.
coordinates.latitude	String	The latitude of the location.
coordinates.longitude	String	The longitude of the location.
status	String	The status of the update (e.g., "Completed", "Failed").
error	String	Any error message, if the update could not be processed.

Example Response

[
  {
    "id": "9b834b4c77124b8f8f0d97b56b7dabc4",
    "externalId": "EXT-001",
    "tripNumber": "TRIP12345",
    "loadNumber": "LOAD12345",
    "eventType": "Location",
    "sharedAt": "2024-11-11T15:02:49.233Z",
    "destination": "Los Angeles, CA",
    "truckNumber": "TRK98765",
    "driverName": "John Doe",
    "trailerNumber": "TRL12345",
    "stopId": "STOP001",
    "locationId": "LOC001",
    "sharedBy": "TMS System",
    "reason": "NA",//Normal Appointment
    "address": {
      "street": "123 Main St",
      "city": "Los Angeles",
      "state": "CA",
      "zipCode": "90001"
    },
    "coordinates": {
      "latitude": "34.052235",
      "longitude": "-118.243683"
    },
    "status": "Completed",
    "error": ""
  }
]

Rate Limits

All endpoints are subject to rate limits to protect the API from traffic spikes. For detailed information on rate limits, please refer to the Rate Limits section.

This page is interactive, allowing you to try a request by completing the fields for the parameters below. As you fill out the parameters, the CURL command on the right side of the page will be automatically updated. Alternatively, you can fork our Public API Postman Collection directly. Make sure to authorize yourself before trying a request.