Error / Warnings codes
Request validation, functional, warning and technical codes returned by the DJUST APIs
Request validation errors
Request validation errors are returned with an HTTP400when a parameter or a payload field does not satisfy a constraint of the contract (bounds, size, format, required value).
The response body follows the same shape on every route:
{"errors":[{"code":"INV0001","message":"nbPreviewLines : must be less than or equal to 100","detail":"nbPreviewLines"}]}| Field | Description |
|---|---|
code | INV0001 — a stable code used whenever the violated constraint carries no dedicated functional code. |
message | Human-readable message, prefixed by the name of the offending field. |
detail | Name of the field concerned, so it can be mapped back to a form input without parsing the message. |
Tip: Readdetailto locate the offending field, and treatINV0001as a single generic validation code. Do not parsemessageto derive behaviour — its wording depends on the constraint.
Backward compatibility: errors that already carried a functional code (the F-E-XXX codes below) keep exactly the same code and message; only the detail is enriched with the field name. Handling of those codes is unchanged.
Functional error codes
Functional error codes are returned by the DJUST API when a request cannot be processed due to invalid input, missing data, or business rule violations.
| Error code | HTTP | Error message | Description |
|---|---|---|---|
| F-E-001 | 422 | Required field {fieldName} is missing or blank | A required field is missing or empty in the request payload. |
| F-E-002 | 404 | At least one {fieldName} does not exist in Djust system : {unknownFieldValues} | The field references an entity that must already exist in DJUST (e.g. an external ID used for an update). |
| F-E-003 | 409 | Unique reference {fieldName} already exists in Djust system | The field contains a reference that already exists. Since it must be unique, the request is rejected. |
| F-E-004 | 422 | Wrong format for field {fieldName}, expected standard URL format | Deprecated - use F-E-012. The field does not match the expected URL format. |
| F-E-005 | 422 | Wrong format for field {fieldName}, expected a number | Deprecated - use F-E-012. The field does not match the expected number format. |
| F-E-006 | 422 | Field {fieldName} has to be {numberCondition} to {value} | The numeric value does not satisfy the required condition (less than, greater than, equal to, etc.) relative to a given threshold. |
| F-E-007 | 422 | Field {fieldName} is not in the correct range, expected a value between {range} | The numeric value falls outside the allowed range. |
| F-E-008 | 422 | Unexpected value for field {fieldName}, must be one of {enumValues} | The provided value is not part of the predefined list of accepted values. |
| F-E-009 | 422 | Wrong format for field {fieldName}, expected a boolean | Deprecated - use F-E-012. The field does not match the expected boolean format (true or false). |
| F-E-010 | 422 | Size limit exceeded for field {fieldName}, must be lower than {limitSize} characters | The field value exceeds the maximum allowed character length. |
| F-E-011 | 422 | Missing mandatory attributes {missingAttributes} required for classification category {classificationCategoryName} / {classificationCategoryId} | Required attributes for the classification category linked to the product are missing. |
| F-E-012 | 422 | Field {fieldName} does not respect expected format {fieldType} | The field does not match the expected format (type, number, boolean, URL, email, phone, etc.). |
| F-E-013 | 422 | No price range defined for quantity = 1 | No price range exists for this offer at quantity 1. At least a unit price must be defined. |
| F-E-014 | 422 | Incorrect offer type value, expected ACCOUNT | When a valid external account ID is provided on an offer, the offer type must be ACCOUNT. |
| F-E-015 | 422 | maxOrderQuantity can not be lower than minOrderQuantity | The maximum order quantity must be greater than or equal to the minimum order quantity. |
| F-E-016 | 422 | The number of {fieldName} elements is limited to {maxListSize} | The number of elements in the list exceeds the allowed maximum. |
| F-E-017 | 422 | Ambiguous reference for fields {fieldName1}, {fieldName2}, can't proceed to treatment. | Two references were provided and the system cannot determine which one to use. |
| F-E-020 | 409 | New classification category detected. Change is unauthorized due to conflict with this attribute setting variant : {attributeName} | Classification category change is not allowed because the product cannot switch between variant and non-variant modes. |
| F-E-028 | 409 | Unauthorized operation {operationType} : {object} must not be in status {unauthorizedStatus} to perform this operation. | The operation is not allowed on an entity in its current status. |
| F-E-030 | 403 | Permission denied. User {userId} with the role {roleName} is not allowed to perform this action on entity {entityType} with id {entityId}. | The caller does not have the required permissions to perform this action. |
| F-E-032 | 401 | Unauthorized. Missing or invalid authentication token. | Authentication failed. The token is missing or invalid. |
| F-E-036 | 409 | Unauthorized operation {operationType}. The entity {entityType} (ID : {entityId}) is not linked to {entityType} (ID : {entityId}). | The operation is not allowed because the entity is not linked to the expected related entity. |
| F-E-039 | 422 | No eligible {entityName} can be processed under current constraints. | After applying business rules and constraints (visibility, status, dates, catalog views, min and max bounds, stock, etc.), no candidate item remains eligible. Not used for invalid inputs, unknown references or uniqueness conflicts (see F-E-001, F-E-002, F-E-003, F-E-008). |
| F-E-040 | 422 | Incompatible combination of fields values. Field {fieldName1} has to be {condition} to {fieldName2}. | The relational constraint between two fields is not satisfied (e.g. startDate must be before endDate). |
| F-E-042 | 409 | Only one active {entityType} is allowed at a time for the provided scope. | A unique-active constraint prevents creating a new resource while another one is already in a non-terminal state. |
Functional warning codes
Functional warnings indicate issues detected on individual entities during validation or synchronization. Each warning carries ablockedflag: whentrue, the operation is not applied; whenfalse, the change was applied automatically and the warning is informational.
| Warning code | Warning message | Description |
|---|---|---|
| F-W-001 | At least one {fieldName} does not exist in Djust system : {unknownFieldValues} | The field corresponds to a reference that must exist in the DJUST system, for example an external reference used to update an object (an offer, a product, etc.). |
| F-W-004 | Field {fieldName} does not respect expected format {fieldType} | The field does not match the expected format. For example, when importing attributes into the product flow, if the field is a list and the type is TEXT, a warning is issued. |
| F-W-014 | The {entityType} with id {entityId} is inactive. Status is {status}. | The entity exists but cannot be used because it is not ACTIVE. |
| F-W-015 | The {entityType} with id {entityId} is not eligible under current constraints. Reason: {reason}. | The entity is active but not eligible in the current business context (account, store, visibility). |
| F-W-016 | The {entityType} with id {entityId} is not consistent with {linkedEntityType} {linkedEntityId}. Reason: {reason}. | The entity exists but the expected relationship is invalid or inconsistent. |
| F-W-017 | Requested quantity is lower than 0. | The requested quantity is negative. |
| F-W-018 | Requested quantity is lower than the minimum order quantity. | The requested quantity is below the minimum order quantity. |
| F-W-019 | Requested quantity is greater than the maximum order quantity. | The requested quantity exceeds the maximum order quantity. |
| F-W-020 | Requested quantity must be a multiple of item per pack. | The requested quantity is not a valid multiple of the pack size. |
| F-W-021 | Zero quantity is not allowed for this order line. | Zero quantity is not permitted on this line. |
| F-W-022 | Not enough stock available for the requested quantity. | Available stock is insufficient for the requested quantity. |
| F-W-023 | Offer custom field configuration is missing or no longer valid. | A referenced custom field no longer exists in the tenant configuration. |
| F-W-024 | Offer custom field value is invalid. | A custom field value does not match the expected type, format, enum, or constraints. |
| F-W-025 | Required offer custom field value is missing. | A required custom field value is missing on the offer. |
| F-W-026 | Unit price has been updated. | The line unit price was recalculated during synchronization. |
| F-W-027 | Currency has been updated. | The line currency was changed during synchronization. |
| F-W-028 | Tax values have been updated. | Tax values were recalculated during synchronization. |
| F-W-029 | Quantity has been automatically adjusted. | The quantity was automatically adjusted to comply with business rules. |
| F-W-030 | Custom field values have been resynchronised. | Custom field values were rewritten to remain consistent with the current reference. |
| F-W-031 | A new line was created with a quantity of {quantity}. | A new line was automatically created during order synchronization. |
| F-W-032 | A line has been deleted. | A line was automatically deleted during order synchronization. |
| F-W-033 | No valid price information was provided for this line. | The line carries no valid price information. |
| F-W-034 | No valid stock information was provided for this line. | The line carries no valid stock information. |
| F-W-035 | The feature flag {featureFlag} is disabled. | The operation was ignored because the corresponding feature flag is disabled on the tenant. |
| F-W-036 | The {entityType} is not in the store. | The referenced entity does not belong to the current store scope. |
| F-W-037 | The customer user is not related to the {entityType}. | The calling customer user is not linked to the targeted entity (e.g. an order from another account). |
| F-W-038 | Classification category {classificationCategoryId} has been moved from logistic family {oldLogisticFamily} to logistic family {newLogisticFamily}. | The classification category changed logistic family during an import or update. |
| F-W-039 | Location {locationId} has been moved from shipping zone {oldShippingZone} to shipping zone {newShippingZone}. | The location changed shipping zone during an import or update. |
| F-W-040 | Unique reference {fieldName} already exists in Djust system. | Non-blocking variant of F-E-003. The provided unique reference (e.g. the externalId of a logistic order line, unique across the tenant) is already used by another entity: the line is skipped and the rest of the batch proceeds. |
Technical error codes
Technical error codes indicate unexpected system-level failures. They usually warrant a retry or contacting DJUST support.
| Error code | Error message | Description |
|---|---|---|
| T-E-001 | Unexpected error : operation {operationType} on entity {entityType} could not be correctly processed. Please retry later. | A technical operation (create, update, delete) could not be processed. Please retry later. |
| T-E-002 | An unexpected error occurred while communicating with an external partner. Operation: {operationType}. Please retry later or contact support. | A third-party provider returned an unexpected error that is not explicitly handled by DJUST. The operation may be partially completed. |
Updated 3 days ago
Did this page help you?