Downloading a list of archived freights created in the company accounts both via API and on the Trans.eu Platform. Endpoint returns freights in closed freight status.
The returned results are paginated with maximum of 30 per page.
For download accepted freights visit Get accepted freights list, for download new and active freights visit Get freights list.
GET
/ext/freights-api/v1/archive
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.
- Filtering — allows you to download a list according to specified criteria
- Sorting — allows you to arrange the results in the specified order
- Pagination — allows you to download results from a specific list page
- Fields selection — allows you to download a list with a limited number of fields for each result
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/archive 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)
Filters
The results will be limited according to the specified conditions.
| Filtered freight field | Filter example |
| truck body | /ext/freights-api/v1/archive?filter={"truck_body_type":"cooler"} |
| truck bodies | /ext/freights-api/v1/archive?filter={"truck_body_types":["box","curtainsider"]} |
| loading place | /ext/freights-api/v1/archive?filter={"loading_place":{"country":"it","postal_code":"88100"}} |
| unloading place | /ext/freights-api/v1/archive?filter={"unloading_place":{"country":"pl","postal_code":"53-146"}} |
| loading date | /ext/freights-api/v1/archive?filter={"loading_date":{"start_date":"2025-01-29","end_date":"2025-02-12"}} |
| unloading date | /ext/freights-api/v1/archive?filter={"unloading_date":{"start_date":"2025-01-31","end_date":"2026-02-18"}} |
Sorting
The results will be arranged in the specified order.
| Sorted freight field | Filter example |
| freight status | /ext/freights-api/v1/archive?sortBy=status |
| loading date | /ext/freights-api/v1/archive?sortBy=loading_date |
| unloading date | /ext/freights-api/v1/archive?sortBy=unloading_date |
| creation date | /ext/freights-api/v1/archive?sortBy=created_at |
You can sorting in ascending or descending mode by adding order parameter with value asc or desc. Example:
/ext/freights-api/v1/archive?sortBy=created_at&order=descPagination
The results will be downloaded from a specific list page. Each page contains maximum of 30 results.
/ext/freights-api/v1/archive?page=2Fields selection
The results will be downloaded only with the list of fields specified in the query. List of available fields for the query is mentioned below in Response Fields table.
Example Request 1
The id, shipment_external_id and loading place fields are returned.
/ext/freights-api/v1/archive?fields={"id":true,"shipment_external_id":true,"loading":true}Example Request 2
All fields are returned except the publication section.
/ext/freights-api/v1/archive?fields={"publication":false}Response Fields
| Attribute | Type | Example | Description |
| archived_at | String | “2025–02-17T13:06:36+01:00” | Freight archiving time |
| 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+01:00” | Freight creation date |
| 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 and time 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 |
| requirements | Object | Main transport requirements | |
| requirements.transport | Object | Transport details | |
| requirements.transport.count | Int | 3 | Number of all transports in freight — only occurs for multi_ftl transport type |
| requirements.transport.remaining | Int | 1 | Number of remaining transports in freight — only occurs for multi_ftl transport type |
| requirements.transport.settlement | String | route | Type of settlement. Available values: route, ton. |
| requirements.transport.settlement_basis | String | loading | Settlement basis. No values for route. Acceptable values for ton: loading, unloading |
| shipment_external_id | String | 2023/NWX/1/3 | External identification number |
| status | String | new | Freight status. See other statuses. |
| 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 and time 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
[
{
"archived_at": "2026-02-10T06:12:42+01:00",
"contact_employees": [
{
"last_name": "Jan",
"name": "Nowakowski",
"trans_id": "1007374-1"
}
],
"created": "2026-02-06T14:40:08+01:00",
"ftl": false,
"height": null,
"id": 3815468,
"length": null,
"loading": {
"coordinates": {
"latitude": 53.601226847,
"longitude": 21.417734311
},
"place": {
"country": "pl",
"locality": "Wroclaw",
"postal_code": "53-146"
},
"timespans": {
"begin": "2026-02-09T14:40:06+01:00",
"begin_local": "2026-02-09T14:40:06+01:00",
"end": "2026-02-09T16:40:06+01:00",
"end_local": "2026-02-09T16:40:06+01:00",
"timezone": "Europe/Warsaw"
}
},
"publication": {
"end_reason": "timeout",
"id": 3290464,
"is_quick_pay": false,
"is_recommended": false,
"is_shared": false,
"price": {
"currency": "eur",
"period": {
"days": null,
"payment": null
},
"value": null
},
"publish_date": "2026-02-06T14:40:08+01:00",
"publish_type": "exchange",
"received_offers": null,
"receivers": {},
"refresh_from": null,
"sent_offers": 1,
"sent_to": {
"companies": true,
"corporate_exchange": null,
"direct": false,
"private_exchange": false
},
"smart_match_offers": null,
"status": "finished"
},
"reference_number": "FR/2026/02/06/22V5",
"requirements": {
"transport": {
"count": null,
"remaining": null,
"settlement": null,
"settlement_basis": null
}
},
"shipment_external_id": null,
"status": "closed",
"temperature": {
"max": null,
"min": null
},
"transit_time": null,
"transport_type": "ltl",
"truck_bodies": [
"curtainsider"
],
"unloading": {
"coordinates": {
"latitude": 50.801536987,
"longitude": 13.076077393
},
"place": {
"country": "de",
"locality": "Nürnberg",
"postal_code": "09876"
},
"timespans": {
"begin": "2026-02-12T14:40:06+01:00",
"begin_local": "2026-02-12T14:40:06+01:00",
"end": "2026-02-12T16:40:06+01:00",
"end_local": "2026-02-12T16:40:06+01:00",
"timezone": "Europe/Berlin"
}
},
"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"
}
}
}Example error 2
Incorrect query
{
"detail": "Failed Validation",
"status": 422,
"title": "Unprocessable Entity",
"type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html",
"validation_messages": {
"filter": {
"truck_body_types": {
"notArray": "Given value must be valid array"
}
}
}
}