Guides
Changelog
Back to All
Added

Tender Endpoints Now Available in the Public API

about 1 month ago

Release Date: November 2025 (tender ingest), June 19, 2026 (public availability)

What's New?

The Public API now includes a full set of Tender endpoints, covering the complete tender lifecycle — create, update, cancel, search, and respond (accept / reject). Originally introduced as an EDI-focused add-on, the Tenders API is now part of the standard public Swagger group and available to all Public API consumers.

What Changed?

Previously, tender operations were only available through EDI integrations or as a restricted add-on.

Now, the Public API includes:

POST /api/p/v{version}/tenders/search
GET  /api/p/v{version}/tenders/{tenderId}
POST /api/p/v{version}/tenders
POST /api/p/v{version}/tenders/update
POST /api/p/v{version}/tenders/cancel
POST /api/p/v{version}/tenders/{tenderId}/accept
POST /api/p/v{version}/tenders/{tenderId}/accept-updates
POST /api/p/v{version}/tenders/{tenderId}/accept-cancel
POST /api/p/v{version}/tenders/{tenderId}/reject
  • Search & get — query tenders and retrieve full tender detail.
  • Create / update / cancel — ingest load tenders (including EDI 204-originated tenders) programmatically.
  • Accept / reject — respond to a tender; accepting creates the corresponding load in Alvys.
  • Accept updates / accept cancellation — apply an inbound tender update or cancellation to the linked load.

Pairs with the tender lifecycle webhook events (tender.received, tender.updated, tender.cancelled, and related events) announced separately — subscribe to webhooks for real-time notification, then act on the tender via these endpoints.

Why?

Tendering is the front door of the load lifecycle. Exposing it in the Public API lets brokers, shippers, and integration platforms route freight into Alvys — and respond to it — without requiring a traditional EDI pipeline.