Skip to main content
In the events of API request errors, OPLOG.ONE uses conventional HTTP response codes in the 4XX and 5XX range to indicate the reason behind the error.
OPLOG.ONE uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing, a duplicate reference number already exists, etc.), and codes in the 5xx range indicate an error with OPLOG.ONE’s servers.

HTTP Status Codes


OPLOG Error Code Reference

Here you will find the error codes and descriptions you may encounter during various operations in the OPLOG API. Error codes are categorized by operation type.

Error Code Usage Tips

General Rules

  • Required Fields: Related error codes are returned for required fields left empty
  • Format Checks: Field name and expected format are specified for invalid format errors
  • Character Limits: Maximum character limits are defined for each field
  • Uniqueness: SKU, Barcode, and Reference numbers must be unique

General Error Codes

Error codes you may encounter in general system and integration errors:

System Errors

Integration Errors

Resource and URL Errors


Sales Order Error Codes

Error codes you may encounter during order creation, update, and management operations:

Reference Number Errors

Address Validation Errors

Address Character Limit Errors

Customer Information Errors

Product and Quantity Errors

Payment Errors

CoD (Cash on Delivery) Errors

Cargo Errors

Same Day Delivery Errors

Gift and Additional Services

Order Status Errors


Receiving Order Error Codes

Error codes you may encounter during receiving operations:

Product Error Codes

Error codes you may encounter during product definition and management operations:

SKU and Barcode Errors

Required Field Errors

Product Management Errors


Error Response Format

When an error occurs, OPLOG.ONE returns a structured error response:
Error Handling Best Practice: Always check the errorCode and property fields to programmatically handle specific error scenarios in your application. Use requestId for support inquiries.