ADM-ORDER-201 - Update Logistic Order

Overview

Updates specific fields of an existing logistic order identified by logisticOrderId.

User scoping

Admin endpoint. Only operator users can call this endpoint (dj-client: OPERATOR).

Store scoping

The effective store context is derived from the dj-store and dj-store-view headers when provided.

The store context does not modify the store assignment of the logistic order.

Updatable fields

This endpoint allows updating the following fields:

  • externalId
  • shippingTrackingUrl
  • customFieldValues

Partial update rules

Only the fields explicitly provided in the request body are updated.

Fields omitted from the request body are left unchanged.

Providing externalId as an empty string clears the existing external identifier.


Providing shippingTrackingUrl as an empty string clears the existing tracking URL.

Business rules

Updating externalId does not impact the internal logistic order identifier, the order lifecycle status, or any downstream processing already performed on the order.

Errors

Returns validation errors (400), authentication errors (401), authorization errors (403), not found errors (404), and unexpected server errors (500).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Logistic order identifier.

Body Params

Logistic order partial update payload.

customFieldValues
array of objects

List of custom field values to apply to the logistic order.

Each entry targets one custom field by its internal Djust ID via the customFieldId field.

Note: FOC endpoints (v1/v2 shop) use the external ID instead.

customFieldValues
string

External identifier of the logistic order.

This value is used to map the logistic order with an external system reference.

When set to an empty string, the existing external identifier is cleared.

string

Shipping tracking URL used to follow delivery status.

When set to an empty string, the existing tracking URL is cleared.

Headers
string
enum
required

Specifies the client type making the request.

  • OPERATOR: Platform operator user.

  • ACCOUNT: Customer account user.

  • SUPPLIER: Supplier managing orders.

Allowed:
string
required

API key required for authentication. Must be valid and linked to the requesting user.

string

(Optional) Store ID in multi-store environments.

string

(Optional) Store view ID in multi-store environments.

Responses
204

No Content (logistic order updated)

400

Bad request (invalid payload)

401

Unauthorized (invalid or missing API key)

403

Forbidden (insufficient permissions)

404

Not found (unknown logistic order)

500

Internal server error

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!