Get accepted freights list

Down­load­ing a list of accept­ed freights cre­at­ed in the same cus­tomer (com­pa­ny) account both via API and on the Trans.eu Plat­form.
End­point returns freights in accept­ed freight sta­tus.
The returned results are pag­i­nat­ed with max­i­mum of 30 per page.

For down­load active and drafts freights vis­it Get freights list, for down­load archived freights vis­it Get archived freights list.

GET
/ext/freights-api/v1/accepted

This method sup­ports query mod­i­fiers that allow you to cus­tomize the list of returned results to your own needs. The list of all para­me­ters is spec­i­fied below in Query Para­me­ters.

  • Search­ing — Allows you to find freight with a giv­en reference_number
  • Pag­i­na­tion — allows you to down­load results from a spe­cif­ic list page
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.

Successful Response
Request Header
GET /ext/freights-api/v1/accepted 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}
Request Parameters (Query)
Searching

It is pos­si­ble to search for results by fil­ter­ing the reference_number field.

After the “val­ue” key­word, you must pro­vide the reference_number val­ue or just a frag­ment of that val­ue. All accept­ed freight that meets the spec­i­fied cri­te­ria will be dis­played.

Exam­ples:

/ext/freights-api/v1/accepted?search={"value":"200W"}

/ext/freights-api/v1/accepted?search={"value":"FR/2023/05/26/2ONGO"}
Pagination

The results will be down­loaded from a spe­cif­ic list page. Each page con­tains max­i­mum of 30 results.

/ext/freights-api/v1/freights?pagination=2
Response Fields
AttributeTypeExam­pleDescrip­tion
contact_employeesArray of ObjectsList of employ­ees assigned to freight nego­ti­a­tion. Default is pub­lish­er.
contact_employees.last_nameStringNowakSur­name of assigned employ­ee
contact_employees.nameStringJanFirst name of assigned employ­ee
contact_employees.trans_idString13443–1Tran­sId of assigned employ­ee
cre­at­edString“2025–02-13T13:06:36.000Z”Freight cre­ation date (UTC for­mat)
ftlBooleanTrueIndi­ca­tion whether the freight is of type FTL (full truck load)
heightFloat3.1Vehi­cle height (range: 0.01–10)
idInt234923Freight iden­ti­fi­ca­tion num­ber, assigned auto­mat­i­cal­ly dur­ing cre­ation of a new freight.
lengthFloat12Vehi­cle length (range: 0.01–100)
load­ing (see details)ObjectPlace of load­ing
pub­li­ca­tion (see details)ObjectPub­li­ca­tion details
reference_numberStringFR/2025/12/30/2NNQFreight ref­er­ence num­ber — a unique, auto­mat­i­cal­ly assigned busi­ness iden­ti­fi­er of the freight
shipment_external_idString2023/NWX/1/3Exter­nal iden­ti­fi­ca­tion num­ber
sta­tusStringnewFreight sta­tus. See details in Freight cre­ation.
tem­per­a­tureObjectRequired freight trans­port tem­per­a­ture. It can be set only for the fol­low­ing truck bod­ies: cooler, isotherm, hook-truck.
temperature.maxFloat3Max­i­mum tem­per­a­ture
temperature.minFloat-5.5Min­i­mum tem­per­a­ture
transit_timeInt460Time expressed in min­utes (pos­i­tive inte­ger) for trans­port, if spec­i­fied.
transport_typeStringftlPos­si­ble val­ues for trans­port type: ftl, ltl, multi_ftl.
truck_bodiesArray of String[“box”,“curtainsider”]Vehi­cle body types set in freight (see dic­tio­nary).
unload­ing (see details)ObjectPlace of unload­ing
vehicle_sizeString“lorry_solo”Vehi­cle sizes set in freight. Basic or Com­pos­ite vehi­cle size name accord­ing to dic­tio­nary.
vol­umeFloat21Vehi­cle vol­ume (range 0.01–10000).
widthFloat3.1Vehi­cle width (range 0.01–10).
Response Body
[
    {
        "contact_employees": [
            {
                "last_name": "Nowak",
                "name": "Jan",
                "trans_id": "1007374-1"
            }
        ],
        "created": "2026-02-17T06:21:53.000Z",
        "ftl": null,
        "height": null,
        "id": 3824591,
        "length": null,
        "loading": {
            "place": {
                "country": "pl",
                "locality": "Wroclaw",
                "postal_code": "54-128"
            }
        },
        "publication": {
            "auction_id": "f10eea08-1522-43fc-8966-b21b7b7bfb0f",
            "end_reason": null,
            "id": 3299125,
            "is_quick_pay": false,
            "is_recommended": null,
            "is_shared": null,
            "offer_id": "20e56393-abde-4aa6-83ff-918cd5eca8a6",
            "price": {
                "currency": "eur",
                "period": {
                    "days": 5,
                    "payment": "deferred"
                },
                "value": 50
            },
            "publish_date": "2026-02-17T06:23:49.000Z",
            "publish_type": "exchange",
            "received_offers": null,
            "receivers": null,
            "refresh_from": null,
            "sent_offers": null,
            "sent_to": null,
            "smart_match_offers": null,
            "status": "finished",
            "stock_id": null
        },
        "reference_number": "FR/2026/02/17/2NNW",
        "shipment_external_id": "1111",
        "status": "accepted",
        "temperature": {
            "max": null,
            "min": null
        },
        "transit_time": null,
        "transport_type": "ltl",
        "truck_bodies": [
            "curtainsider"
        ],
        "unloading": {
            "place": {
                "country": "de",
                "locality": "Nürnberg",
                "postal_code": "09876"
            }
        },
        "vehicle_size": "any_size",
        "volume": null,
        "width": null
    },
]

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

Incor­rect field in query

{
    "detail": "Failed Validation",
    "status": 422,
    "title": "Unprocessable Entity",
    "validation_messages": {
        "sortBy": {
            "notInArray": "Allowed values: status, created_at, loading_date, unloading_date, archived_at"
        }
    }
}