1. Trans.eu Api
  2. General information
  3. API Callback URLs

API Callback URLs

Call­back URL is used to auto­mat­i­cal­ly receive noti­fi­ca­tions about events from Trans.eu Plat­form. When a spe­cif­ic event occurs, the Trans.eu sys­tem sends a request with event data to the call­back URL you pro­vid­ed, allow­ing your appli­ca­tion to react with­out con­stant­ly polling for updates. This solu­tion can be used for objects cre­at­ed via API requests, such as freights, orders, announce­ments and time win­dows.

To receive noti­fi­ca­tions about events:

1. Pro­vide the callback_url field in the request cre­at­ing the object with a return address — call­back address should start with pro­to­col (http:// or https://)

"callback_url": "http://example.com/msg"

2. Send the object via API with select­ed POST method request

Method: POST
Endpoint: /ext/freights-api/v1/freight-exchange
Endpoint: /ext/freights-api/v1/freight-employees
Endpoint: /ext/freights-api/v2/freights
Endpoint: /ext/freights-api/v1/freight-companies
Endpoint: /ext/freights-api/v1/freight-auto
Endpoint: /ext/freights-api/v1/private-exchange
Endpoint: /ext/freights-api/v1/freight-corporate
Endpoint: /ext/orders-api/v1/orders-created
Endpoint: /ext/dock-scheduler-api/v1/announcement
Endpoint: /ext/dock-scheduler-api/v1/warehouse/timeWindow

3. Lis­ten for receive events at the address spec­i­fied in callback_url — see the exam­ple response oppo­site

{
"id": "87795",
"event_name": "{freights.proposal_request.negotiated}",
"occurred_at": "2026-01-25T11:41:11+00:00",
"data": {
        "price": 560.20,
        "author": "12665-1"
      }
}
Callback flow
Callback Flow
Structure of event
Event field nameEvent field typeExam­pleEvent field descrip­tion
idInte­ger“87795”Freight id in freight events.
Order id in order events.
Time win­dow id in Dock Sched­uler events.
event_nameString“{freights.proposal_request.negotiated}”Event name giv­en in brack­ets {}
occured_atString (UTC time­stamp with off­set)“2026–01-25T11:41:11+00:00”Time of event occur­rence
dataObjectOption­al sec­tion with event-spe­cif­ic infor­ma­tion. It is described in Data sec­tion col­umn in the table below.
List of freight events received to callback URL
Event nameDescrip­tionData sec­tion
freights.freight.createCre­at­ing a new freight
freights.freight.updateFreight data update
freights_processing.publication.finishedEnd of freight pub­li­ca­tion. There may be a dupli­ca­tion with the event freights.publication.finished.
freights_processing.publication.negotiation_time_finishedEnd of nego­ti­a­tion time for car­ri­er
freights.proposal_request.acceptedAccep­tance of the freight offer by the nego­ti­at­ing par­tic­i­pant, indi­cat­ing the offered price. If the accep­tance was made by the pub­lish­er or the pub­li­ca­tion includ­ed the “is_first_buy” option, the pub­li­ca­tion will be fin­ished.price (float type) — a price accept­ed dur­ing nego­ti­a­tion
freights.proposal_request.createdStart of a new nego­ti­a­tion. This event is always sent in par­al­lel with the event of a new offer being made or an offer being accept­ed (with the “is_first_buy” pub­li­ca­tion option).
freights.proposal_request.negotiatedSub­mis­sion of a new price offer by a par­tic­i­pant in the nego­ti­a­tions.price (float type) — a new price offered in nego­ti­a­tion
author_id (String type) — tran­sId of the user sub­mit­ting the offer
freights.proposal_request.negotiation_lostClos­ing nego­ti­a­tions with the los­ing par­tic­i­pant. Event sent for each los­ing par­tic­i­pant.id (Int type) — user’s com­pa­ny offi­ceid
author_id (String type) — tran­sid of the nego­ti­at­ing user
participant_company_id (Int type) — user’s com­pa­ny offi­ceid
freight_id (Int type) — iden­ti­fi­ca­tion num­ber of the nego­ti­at­ed freight
freights.proposal_request.rejectedA nego­ti­a­tion par­tic­i­pant rejects the nego­ti­a­tion. Nego­ti­a­tions between these par­tic­i­pants will not be able to be restart­ed.
freights.proposal_request.renouncedA nego­ti­a­tion par­tic­i­pant rejects the nego­ti­a­tion. Nego­ti­a­tions between these par­tic­i­pants may be restart­ed.
freights.proposal_request.withdrawnWith­draw­al of the sub­mit­ted offer by a par­tic­i­pant in the nego­ti­a­tions.
freights.publication.acceptedAccep­tance of the pub­lished freight by the car­ri­er
freights.publication.activatedActi­va­tion of freight pub­li­ca­tion
freights.publication.canceledCan­celling freight pub­li­ca­tion
freights.publication.createdCre­ation of new pub­li­ca­tion
freights.publication.finishedEnd of freight pub­li­ca­tion. There may be a dupli­ca­tion with the event freights_processing.publication.finished.
List of order events received to callback URL
Event nameDescrip­tionData sec­tion
freight_orders.order.attachment_addedAdding an attach­ment to the order
freight_orders.order.attachment_removedRemov­ing an attach­ment from the order
freight_orders.order.attachment_visibility_changedThe vis­i­bil­i­ty of the order attach­ment has changed
freight_orders.order.createdCre­at­ing a new order (from freight)
freight_orders.order.delivery_was_confirmedCon­fir­ma­tion by the client of order deliv­ery.freight_id - freight id asso­ci­at­ed with the order
freight_reference_number - auto­mat­i­cal­ly assigned busi­ness iden­ti­fi­er of the freight
shipment_external_id - exter­nal iden­ti­fi­ca­tion num­ber
status - order sta­tus, always here “deliv­ery-con­firmed”
freight_orders.order.order_was_accepted_by_contractAuto­mat­ic accep­tance of an order based on an fixed route
freight_orders.order.order_was_cancelledCan­cel­ing the order
freight_orders.order.proposal_submittedPro­pos­al to change the terms of the order
freight_orders.order.proposal_was_acceptedAccep­tance of the terms of the order
freight_orders.order.shipment_external_id_was_changedThe exter­nal ship­ment num­ber has changed
freight_orders.order.transports_was_finishedCon­fir­ma­tion by the car­ri­er of unload­ing of all trans­ports in the orderfreight_id - freight id asso­ci­at­ed with the order
freight_reference_number - auto­mat­i­cal­ly assigned busi­ness iden­ti­fi­er of the freight
shipment_external_id - exter­nal iden­ti­fi­ca­tion num­ber
status - order sta­tus, always here “wait­ing-for-con­fir­ma­tion”
freight_orders.order.vehicle_and_driver_have_changedUpdat­ing vehi­cle and dri­ver data.
Dep­re­cat­ed event, replaced by transports.transport.devices_set_changed event.
List of Transports in realization events received to callback URL
Event nameDescrip­tionData sec­tion
transports.transport.devices_set_changedUpdat­ing vehi­cle and dri­ver data in a sin­gle trans­port with­in an ordercarrier_id - Con­trac­tor’s office Id
carrier_name - Con­trac­tor’s name
executor_name - Dri­ver’s name and sur­name
executor_phone - Dri­ver’s phone num­ber
freight_id - freight id asso­ci­at­ed with the order
freight_reference_number - auto­mat­i­cal­ly assigned busi­ness iden­ti­fi­er of the freight
order_id - Order id
order_number - auto­mat­i­cal­ly assigned order num­ber
semitrailer_plate_number - trail­er plate num­ber, if occurs
shipment_external_id - exter­nal iden­ti­fi­ca­tion num­ber
truck_plate_number - truck plate num­ber
List of Dock Scheduler events received to callback URL
Event nameDescrip­tionData sec­tion
time_slot_management.announcement.createdCre­ation of announce­ment
time_slot_management.announcement.deletedDele­tion of announce­ment
time_slot_management.announcement.updatedUpdat­ing announce­ment data
time_slot_management.time_window.createdCre­at­ing a time win­dow
time_slot_management.time_window.deletedDelet­ing a time win­dow
time_slot_management.time_window.updatedUpdat­ing time win­dow data