Skip to main content
The Zinc API uses conventional HTTP response codes to indicate the success or failure of an API request.

HTTP Status Codes

Error Response Format

All error responses follow a consistent structure:

API Error Codes

General Errors

Example

Authentication Errors

Example

Wallet & Payment Errors

Example

Order Request Errors

Example

External Service Errors

Example

Order Processing Errors

When an order fails during processing, the error_type field in the order response or webhook payload contains one of these codes:

Structured error details

Alongside the flat error and error_type keys (kept for backward compatibility), a failed job result may include an error_details object. This is the structured home for enrichment beyond the category and message — for example, the specific reasons a shipping address was rejected, or which fields failed validation. Each entry in field_errors is a FieldError:

Example

Product Errors

Example

Price Errors

Example

Cart & Checkout Errors

Example

Gift Errors

An order submitted with is_gift: true fails with this error type rather than being placed as a normal order — a gift arriving with prices visible to the recipient is treated as worse than no order. If gifting is an optional add-on in your flow, catch this error type and retry without is_gift to place the order as a standard purchase. See Gift orders.
gift_message does not fail this way. Where a retailer’s checkout has no gift-message field, the order is still placed without the message.

Example

Shipping Errors

Example

Payment Errors

Example

Account Errors

Example

Retailer Errors

Example

Quantity Limit Errors

Example