1. Trans.eu Api
  2. Orders
  3. Order confirmations
  4. Confirm order unloading

Confirm order unloading

Request allows you to report com­ple­tion of unload­ing select­ed trans­porta­tion order. You can con­firm unload­ing togeth­er with the arrival con­fir­ma­tion or skip this step.
It is avail­able for sent and received orders for Ship­pers and Car­ri­ers.

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

POST
/ext/orders-api/v1/orders-created/{order-id}/unloaded
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

Request Para­me­ters

Request Body

Successful Response

Response Body

Error Response

Client errors (400)

Gen­er­al API errors

Request Header
POST /ext/orders-api/v1/orders-created/{order-id}/unloaded 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
AttributeTypeExam­pleManda­to­ryDescrip­tion
arrived_atString“2025–10-22T11:00:00+0600”NoDate and time of arrival to unload­ing point.
If a future time is spec­i­fied, the cur­rent time will be record­ed instead.
complete_dateString“2025–10-22T14:00:00+0600”YesDate and time of com­plete unload­ing of the trans­port.
If a future time is spec­i­fied, the cur­rent time will be record­ed instead.
claimsString“dam­aged car­go”NoMust con­tain at least 5 char­ac­ters. if pro­vid­ed, the unload­ing will be marked as “objec­tions raised”.
Example Request Body
{
  "arrived_at": "2026-02-10T11:00:00+0100",  // not mandatory
  "complete_date": "2026-02-10T11:30:00+0100",
  "claims": "damaged cargo"                  // not mandatory
}
Successful Response
204 No Content

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

Claims is too short

{
    "claims": {
        "minLength": "claims must be longer than or equal to 5 characters"
    }
}
Example error 2

No com­plete date

{
    "complete_date": {
        "isDefined": "complete_date should not be null or undefined",
        "isIso8601": "complete_date must be a valid ISO 8601 date string"
    }
}
Example error 3

Attempt to report the com­plete date before arriv­ing to unload

{
    "error": "Unprocessable Entity",
    "message": "transportId: 20a931e4-b43c-4bd1-958f-ab2c2e386299: Complete date cannot be before arrival date.",
    "status_code": 422
}