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

Confirm order delivery

Request allows you to con­firm the exe­cu­tion of the order. Con­firmed order is marked with archived sta­tus.
It is avail­able for sent orders only.

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.

PATCH
/ext/orders-api/v1/orders-created/{order-id}/confirm
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 Body

Error Response

Client errors (400)

Gen­er­al API errors

Request Header
PATCH /ext/orders-api/v1/orders-created/{order-id}/confirm 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}
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

Order does not exists

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

Already con­firmed

{
    "detail": "E018: The delivery for the order a7dbddae-14f0-4bf5-ae26-9792ad76d123 has already confirmed",
    "status": 409,
    "title": "Conflict",
    "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"
}