Downloading a list of accepted freights created in the same customer (company) account both via API and on the Trans.eu Platform.
Endpoint returns freights in accepted freight status.
The returned results are paginated with maximum of 30 per page.
For download active and drafts freights visit Get freights list, for download archived freights visit Get archived freights list.
GET
/ext/freights-api/v1/accepted
This method supports query modifiers that allow you to customize the list of returned results to your own needs. The list of all parameters is specified below in Query Parameters.
- Searching — Allows you to find freight with a given reference_number
- Pagination — allows you to download results from a specific list page
Request Authorization
Every request MUST include a valid access token obtained during the user authorization process, provided using the Bearer token scheme in the Authorization header.
Successful Response
Error 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 possible to search for results by filtering the reference_number field.
After the “value” keyword, you must provide the reference_number value or just a fragment of that value. All accepted freight that meets the specified criteria will be displayed.
Examples:
/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 downloaded from a specific list page. Each page contains maximum of 30 results.
/ext/freights-api/v1/freights?pagination=2Response Fields
| Attribute | Type | Example | Description |
| contact_employees | Array of Objects | List of employees assigned to freight negotiation. Default is publisher. | |
| contact_employees.last_name | String | Nowak | Surname of assigned employee |
| contact_employees.name | String | Jan | First name of assigned employee |
| contact_employees.trans_id | String | 13443–1 | TransId of assigned employee |
| created | String | “2025–02-13T13:06:36.000Z” | Freight creation date (UTC format) |
| ftl | Boolean | True | Indication whether the freight is of type FTL (full truck load) |
| height | Float | 3.1 | Vehicle height (range: 0.01–10) |
| id | Int | 234923 | Freight identification number, assigned automatically during creation of a new freight. |
| length | Float | 12 | Vehicle length (range: 0.01–100) |
| loading (see details) | Object | Place of loading | |
| publication (see details) | Object | Publication details | |
| reference_number | String | FR/2025/12/30/2NNQ | Freight reference number — a unique, automatically assigned business identifier of the freight |
| shipment_external_id | String | 2023/NWX/1/3 | External identification number |
| status | String | new | Freight status. See details in Freight creation. |
| temperature | Object | Required freight transport temperature. It can be set only for the following truck bodies: cooler, isotherm, hook-truck. | |
| temperature.max | Float | 3 | Maximum temperature |
| temperature.min | Float | -5.5 | Minimum temperature |
| transit_time | Int | 460 | Time expressed in minutes (positive integer) for transport, if specified. |
| transport_type | String | ftl | Possible values for transport type: ftl, ltl, multi_ftl. |
| truck_bodies | Array of String | [“box”,“curtainsider”] | Vehicle body types set in freight (see dictionary). |
| unloading (see details) | Object | Place of unloading | |
| vehicle_size | String | “lorry_solo” | Vehicle sizes set in freight. Basic or Composite vehicle size name according to dictionary. |
| volume | Float | 21 | Vehicle volume (range 0.01–10000). |
| width | Float | 3.1 | Vehicle 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 status codes indicate client errors, meaning that the request could not be processed due to an issue on the client side. Below is a list of request-specific errors.
Example error 1
Incorrect 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"
}
}
}