1. Trans.eu Api
  2. Freights section
  3. Refresh publication

Refresh publication

Active freight pub­li­ca­tions can be refreshed every 15 min­utes, updat­ing the pub­li­ca­tion date. Refreshed freight will appear on the top of freight offers list, with­out the need to add a new freight.
Method is avail­able for freights pub­lished to Trans.eu Freight Exchange and pri­vate exchanges.

The freight-id iden­ti­fi­ca­tion num­ber in method call can be tak­en from response after cre­at­ing the freight or by down­load­ing the freight list.

PUT
/ext/freights-api/v1/freights/{freight-id}/refresh_publication
PUT
/ext/private-exchange-api/v1/exchange/{freight-id}/refresh-publication
PUT
/ext/corporate-exchange-api/v1/corporate-exchange/{freight-id}/refresh-publication
Request Authorization

Every request MUST include a valid access token obtained dur­ing the user autho­riza­tion process, pro­vid­ed using the Bear­er token scheme in the Autho­riza­tion head­er.

Request

Request Head­er

Successful Response

Response Fields

Response Body

Error Response

Client errors (400)

Gen­er­al API errors

Request Header
PUT /ext/freights-api/v1/freights/{freight-id}/refresh_publication HTTP/1.1 
Host: api.platform.trans.eu 
Content-Type: application/json
Accept: application/json
Authorization: Bearer {access_token) 
Api-key: {unique_app_api-key}
Response Fields
AttributeTypeExam­pleDescrip­tion
has_been_queuedBooleanFalseA mark­er of whether the refresh request has been accept­ed and queued (True) or has already been exe­cut­ed (False).
refresh_fromString“2025–09-10T10:58:08+01:00”Next pos­si­ble refresh date
Response Body
{
    "has_been_queued": false,
    "refresh_from": "2026-02-10T10:58:08+01:00"
}

Client errors (code 400)

HTTP 4xx sta­tus codes indi­cate client errors, mean­ing that the request could not be processed due to an issue on the client side. Below is a list of request-spe­cif­ic errors.

Example error 1

Freight does not exists

{
    "detail": "Freight not found (id: 381781011)",
    "status": 404,
    "title": "Not Found",
    "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"
}
Example error 2

Incor­rect freight sta­tus to refresh

{
    "message": "Freight is not published"
}
Example error 3

Refresh­ing to ear­ly

{
    "detail": "Refresh unavailable (id: 3293567), last refresh was at '2026-02-10T10:42:02+01:00', available from: '2026-02-10T10:57:02+01:00'",
    "refresh_from": "2026-02-10T10:57:02+01:00",
    "status": 422,
    "title": "Unprocessable Entity",
    "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"
}