API Update: Shipper Reference Field and More

R+L Carriers API – Release Notes
Release Title: Shipper Reference Field and More
Release Date: June 2026

Release Overview

This release includes enhancements and defect resolutions for the Bill of Lading and Pickup Request APIs to improve reliability and expand integration capabilities.

Enhancements

New ShipperReferenceNumber Field

A new ShipperReferenceNumber field has been added to the following endpoints:

• POST /BillOfLading
• POST /PickupRequest/FromBOL

This enhancement enables customers to provide an additional shipper reference number when creating a Bill of Lading and its associated Pickup Request, improving shipment tracking and customer reference capabilities.

Request Example

The ShipperReferenceNumber field should be included within the PickupRequest object as shown below:

{
  "PickupRequest": {
    "PickupInformation": {
      "PickupDate": "string",
      "ReadyTime": "string",
      "CloseTime": "string",
      "AdditionalInstructions": "string",
      "LoadAttributes": [
        "string"
      ]
    },
    "Contact": {
      "Name": "string",
      "CompanyName": "string",
      "PhoneNumber": "string",
      "PhoneExtension": "string",
      "EmailAddress": "string"
    },
    "SendEmailConfirmation": true,
    "ShipperReferenceNumber": "string"
  }
}

Defect Fixes

Digital Council BOL Request Submission

Resolved an issue affecting the following endpoint:

• POST /BillOfLading/DigitalCouncilBOL

Previously, requests could fail to submit when the Notifications array was included but empty. The endpoint now correctly processes requests regardless of whether the Notifications array contains entries.

Pickup Request Response

Resolved an issue where in rare cases failed Pickup Request submissions could return an HTTP 200 OK response while the PickupID value was incorrectly returned as “INVALID”.

The API now correctly provides validation messages for the failed pickups and the correct Pickup ID for successfully created pickup requests.