The endpoint for searching loads requires specifying the API version in the URL path. Including the version number ensures that your application interacts with the correct version of the API, providing stability and compatibility as the API evolves. For more information on how versioning works and how to include it in your requests, please refer to the Versioning page.

Request Parameters

The following parameter is required in the URL path:

ParameterTypeRequiredDescription
versionStringYesThe API version to use.

Request Body Parameters

The version is required in the path parameters. The query request parameters for this endpoint are listed below.

ParameterTypeRequiredDescription
pageNumberNoThe page number for pagination.
pageSizeNumberYesThe number of items per page for pagination. PageSize must be greater than 0.
dateRangeObjectNoThe date range to filter the loads.
dateRange.startStringNoThe start date of the range to filter the createdAt loads.
dateRange.endStringNoThe end date of the range to filter the createdAt loads.
statusArrayConditionallyThe status of the loads to filter. This field is required if the other conditionally required fields are left empty. Statuses: [TONU, Dispatched, In Transit, Queued, Paid, Open, Completed, Financed, Cancelled, Covered, In Review, Released-Carrier Paid, Reserved, Trip Completed, En-Route, Quoted, Admin, Invoiced, Carrier Paid, Released, Delivered]
orderNumbersArrayConditionallyThe order numbers to filter the loads. This field is required if the other conditionally required fields are left empty.
loadNumbersArrayConditionallyThe load numbers to filter the loads. This field is required if the other conditionally required fields are left empty. The maximum number of load I allowed in the search body, loadNumber is 150.
poNumbersArrayConditionallyThe purchase order numbers to filter the loads. This field is required if the other conditionally required fields are left empty.
customerIdStringConditionallyThe customer ID to filter the loads. This field is required if the other conditionally required fields are left empty.
updatedAtRangeObjectNoThe date range to filter loads based on their last update.
updatedAtRange.startStringNoThe start date of the range to filter the updatedAt loads.
updatedAtRange.endStringNoThe end date of the range to filter the updatedAt loads.
updatedByStringConditionallyThe user ID of the person who last updated the loads.This field is required if the other conditionally required fields are left empty.

Example CURL request

Use the Current API version number and make sure to replace the Authorization header value with your actual Bearer token for the request:

curl --location 'https://integrations.alvys.com/api/p/v1/loads/search' \
--header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ...' \
--header 'Content-Type: application/json' \
--data '{
  "page": 0,
  "pageSize": 200,
  "dateRange": {
      "startDate": "2023-09-09T13:09:30.788Z",
      "endDate": "2024-09-09T13:09:30.788Z"
               },
  "status": ["In Transit"],
  "updatedBy" : "0d00f000-1b85-4ed8-000-6a000d1111db",
  "updatedAtRange": {
      "start": "2024-09-09T13:09:30.788Z",
      "end": "2024-10-19T13:09:30.788Z"
  },           
  "orderNumbers": [
         "123456789"
               ],
  "loadNumbers": [
         "123456789"
                 ],
  "poNumbers": [
          "123456789"
               ],
  "customerId": "0e2bb9d5eae342c9bb89f7ac24f01a84"
}

Response Parameters

The following table lists the parameters included in the response for load-related requests.

ParameterTypeRequiredDescription
idStringYesThe unique identifier of the load.
loadNumberStringYesHuman-readable load number, unique by subsidiary.
orderNumberStringNoAn optional external order number.
poNumberStringNoAn optional external Purchase Order number.
customerIdStringYesThe internal Customer ID for the load.
customerNameStringNoNormalized customer name for reporting purposes; can be null for some historical data.
statusStringYesOne of the following: In Review, Open, Quoted, Reserved, Covered, Dispatched, In Transit, Delivered, TONU, Released, Queued, Invoiced, Financed, Completed, Paid, Cancelled.
contractIdStringNoOptional Customer Contract ID.
customerTypeListYesThe type of customer this load is associated with.
fleetObjectNoInformation about the fleet associated with the load.
fleet.idStringNoThe unique identifier of the fleet.
fleet.nameStringNoThe name of the fleet.
fleet.invoiceNumberPrefixStringNoThe invoice number prefix used by the fleet.
invoiceAsStringYesThe subsidiary or company information used when invoicing this load.
linehaulObjectNoThe cost of transporting the load, excluding additional fees such as fuel surcharges or accessorials.
linehaul.amountNumberNoThe numeric value of the linehaul charge.
linehaul.currencyStringNoThe currency of the linehaul charge.
fuelSurchargeObjectNoThe additional charge applied to cover fluctuating fuel costs.
fuelSurcharge.amountNumberNoThe numeric value of the fuel surcharge.
fuelSurcharge.currencyStringNoThe currency of the fuel surcharge.
customerAccessorialsObjectNoAdditional charges beyond the base rate and fuel surcharge, such as detention or lumper fees.
customerAccessorials.amountNumberNoThe numeric value of the accessorial charges.
customerAccessorials.currencyStringNoThe currency of the accessorial charges.
customerRateObjectNoInformation about the rate charged to the customer for the load.
customerRate.amountNumberNoThe numeric amount of the customer rate, which includes all applicable customer accessorials like Linehaul (LH) + Fuel Surcharge (FSC) + Accessorials (ACC).
customerRate.currencyStringNoThe currency of the customer rate.
customerMileageObjectNoInformation about the mileage associated with the load.
customerMileage.distanceObjectNoInformation about the distance details.
customerMileage.distance.valueNumberNoThe numeric value of the distance.
customerMileage.distance.unitOfMeasureStringNoThe unit of measure for the distance, e.g., Miles.
customerMileage.sourceStringNoThe source of the mileage data.
customerMileage.profileIdStringNoThe profile ID used for the mileage data.
customerMileage.profileNameStringNoThe profile name used for the mileage data.
invoicedAmountObjectNoInformation about the total amount invoiced for the load.
invoicedAmount.amountNumberNoThe numeric amount invoiced.
invoicedAmount.currencyStringNoThe currency of the invoiced amount.
weightObjectNoInformation about the weight of the load.
weight.valueNumberNoThe numeric value of the weight.
weight.unitOfMeasureStringNoThe unit of measure for the weight, e.g., Kilograms.
volumeObjectNoInformation about the volume of the load.
volume.valueNumberNoThe numeric value of the volume.
volume.unitOfMeasureStringNoThe unit of measure for the volume, e.g., Gallons.
scheduledPickupAtStringNoScheduled pick-up date and time.
scheduledDeliveryAtStringNoScheduled delivery date and time.
pickedUpAtStringNoActual pick-up time, always in UTC.
deliveredAtStringNoActual delivery time, always in UTC.
invoicedAtStringNoDate and time when the first invoice was generated.
referencesObjectNoInformation about references associated with the load.
references.idStringNoThe unique identifier of the reference.
references.nameStringNoThe name of the reference.
references.valueStringNoThe value of the reference.
references.typeStringNoThe data type of the reference, e.g., Text, Date, Bool, or List.
references.accessStringNoThe access level of the reference, e.g., Internal or Public.
customerAccountManagerIdStringNoThe unique identifier of the Customer Account Manager assigned to the load.
updatedAtStringNoThe date and time when the load was last updated.
updatedByStringNoThe user who last updated the load.

Example Response

On the right side, you can see examples of different error codes by clicking "Example" and selecting the response code.


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.

Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!