TruckMate 2026.1 New Features: Web/APIs

Query parameters traceNumbers and traceType for GET /orders has been marked as deprecated in the Open API Spec.

Fixed an issue where updating a manually-rated order item could accidentally clear the “dimensional weight unit” value. Now, when you change an item on a manually-rated order (like updating pieces), the weight/unit information stays intact.

Fixed memory leaks in ART that could cause increasing memory usage under sustained API traffic. The most common leak occurred during high-volume GET /tm/orders and GET /tm/trips calls with expand parameters. Multiple Delphi object lifetime issues were corrected across the ART server, database connection handling, and data module cache.

GET /orders: improve $filter OR performance for billNumber + traceNumbers predicates to prevent long-running queries/timeouts.

SCHEMA: 187705_IMPROVE_FILTER_OR_PERFORMANCE.SQL

Fixed an issue where POST /tm/orders/:orderId/shipInstructs returned 400 invalidBusinessLogic when both the pickup and delivery client profiles had Customer-Specific set to False. The API now correctly resolves global shipping instructions from the SHIPINSTRUCT table when both clients have Customer-Specific disabled.

Orders API status change endpoint updated to process position statuses.

The traceNumber and traceType query parameters have been marked as deprecated. Please use the $filter parameter with the traceNumbers/traceNumber and/or traceNumbers/traceType fields for related filtering and better performance.

Orders and rate quotes can be viewed in the Customer Service application.

Pickup requests can be viewed in the Order Preprocessor application.

Application configuration options (app configs) can be viewed in the Application Configurator application.

POST orders/shipInstructs — inefficient SQL query causing table scan replaced (performance).

Trips API - Updated GET for /stop Information to display Attempted Delivery (Reattempt) information.

Fixed an issue where BE_DISP_CANCEL_ACTIVE_TRIP was not considered in Trips API. With the fix this security config is respected.

SCHEMA: 186529_CUSTOM_BEFORE_IMC_TRIP_CANCEL.SQL

Fixed an access violation that was being encountered when using the trips API to perform a trip status update using the zoneIdLookup field.

PUT trips/:tripNumber/status

Fixed an issue where a SQL error was being encountered when using vendor web user authentication with the codeBehavior parameter to retrieve trips in the Trips API.

SCHEMA: 187274_FIX_FIELDS_AMBIGUITY_IN_TMS_TRIPS.SQL

Fixed an issue where the reason code was not populated when updating order status via the trip-level REST API endpoint (PUT /trips/:tripNumber/orders/:orderId/status).

No canceled or completed trips visible on the active loads page as expected.

Vendor Active Loads query parameter added to trips endpoint and verified.

Added the ability to apply a reason code on the trip based status update endpoint in the trips API.

PUT trips/{tripNumber}/status

Reason code is now passed into order status history during administrative status change in TruckMate Restful API.

Added PUT /cashReceipts/{id} — update existing cash receipts via API.

Added legDate field to driverPayments endpoint (GET/POST/PUT) as the preferred name for the leg date. The paymentDate field is now deprecated but remains functional for backward compatibility. Added transactionDate to GET responses.

Added GET /cashReceipts and /cashReceipts/{cashReceiptId\] and its child resources to the Finance API.

Finance child POST endpoints now support onlyPostedResults to return only newly created items when true.

Corrected issue with expanding /tripFuelPurchases for the /fuelTaxes endpoint.

The 404 Not Found Contract Tests now returns 404 Not Found with correct error message, not 200OK or 400 Bad Request.

GL Accounts now ensure there is at most one default per (glAccountType + currencyCode) group (per login company) when setting or changing a default.

Fixed an issue in the Finance API regarding Driver Deductions. When a driver has a deduction code with both Admin Fee Deduction and Tax Deduction enabled, these fields were not automatically included in the response. This fix ensures both fields are returned in the response body.

Updated POST /apInvoices/:apInvoiceId/apDriverDeductions API so that, after adding a new driver deduction record to an AP Invoice, the deductionQuantity, deductionRate, deductionAmount, deductionFunctionalTotal, and deductionReference fields will be populated accordingly in the same way as ApNe.exe.

Updated PUT /apInvoices/:apInvoiceId/apDriverDeductions/apDriverDeductionId API so that, after changing the deductionCode specified in the PUT request body, the deductionRate, deductionAmount, deductionFunctionalTotal, deductionReference fields will be re-calculated accordingly in the same way as ApNe.exe.

Updated the PUT /apInvoices/:apInvoice so that, when changing the 'currencyCode' and/or 'glAccount', the following fields will be updated correctly and reflected in the response:

Finance - PUT /apInvoices - "autoForeignExchange": "True" on a foreign currency AP Bill is now working as expected.

Updated the PUT /apInvoice endpoint to ensure that modifying the vendorBillDate correctly triggers the recalculation of the GL Rate, GL Amount, and Functional Amount.

payableAgingDate is now checked based on the selected vendor for AP invoices.

Fixed an issue in POST apInvoices endpoints where -currencyCode and isIntercompany were not set per vendor profile ('Accounts Payable' tab -'Currency' field and 'Inter-Company' checkbox).

The Finance API endpoint PUT /apInvoices has been enhanced to automatically update related dates when the GL Date is modified. For AP invoices where the vendor has "Invoice Date for Aging" turned off, changing the GL Date (vendorBillDate) will now automatically recalculate:

These vendor configurations are set up in Profile.exe. This new behavior also aligns with ApNe.exe.

Fixed PUT /interlinerPayables/:interlinerPayableId to only enforce probillNumber validation during approval (unaudited to audited), allowing normal unaudited to unaudited updates without requiring a probill.

The Finance API endpoint PUT /apInvoices has been enhanced to automatically update related dates when the Invoice Aging Date is modified. For AP invoices where the vendor has "Invoice Date for Aging" turned on, changing the Invoice Aging Date (payableAgingDate) will now automatically recalculate:

These vendor configurations are set up in Profile.exe. This new behavior also aligns with ApNe.exe.

Updated the PUT to /apInvoices to match with the Invoice Entry application when changing the vendor on an existing invoice. A PUT will now update the following invoice settings based on the vendor’s profile (Accounts Payable tab):

Interliner Payables: when updating a payable without providing payableAgingDate, the API now defaults it correctly (instead of 1899-12-30).

Interliner payable updates now enforce import tolerance validation and return a 400 validation error for out-of-tolerance adjustedSubTotal / adjustedExtras updates.

Finance API - interlinerPayables: Corrected an issue where a PUT request that did not include adjustments to sub-total or extra charges would still trigger the adjustedSubTotal to calculate (incorrectly). The adjusted fields will now remain as their correct amounts.

Resolved an issue with the Finance API. When using POST apInvoices to create a new AP Invoice using a vendor profile that has the 'Invoice Date for Aging' checked, a number of fields were not populated correctly.

Added POST cashReceipts/{id}/arPayments.

Added POST cashReceipts/{id}/onAccountPayments

Added PUT cashReceipts/{id}/onAccountPayments/{id}

Added PUT cashReceipts/{id}/arPayments/{id}

Implemented the DELETE finance/cashReceipts/{cashReceiptId}/arPayments/{arPaymentId} and call central common validation to validate a DELETE can occur. OpenAPI also updated.

Implemented the DELETE finance/cashReceipts/{cashReceiptId} and call central common validation to validate a DELETE can occur. OpenAPI also updated.

Renamed onAccountCredits resource to onAccountPayments.

Finance API — AP invoices: GET /apInvoices/expenses responses now include expense bill rate and bill amount as expenseBillRate and expenseAmountInInvoiceCurrency.

Added optional isBillRate support to /apInvoices expense handling to control whether invoice-currency (BILL\_RATE/BILL\_AMT) or base-currency (TX\_RATE/TX\_AMT) values are used and updated; default remains false for backward compatibility with TM25.4.

Verified PUT/POST/DELETE have been hidden and are no longer visible in the Open API Spec.

Fixed an issue in the GET tm/reports endpoint where the related temporary files were not being cleaned out of the Windows SystemTemp directory.