LogoLogo
System status
Commerce API references
Commerce API references
  • Commerce API references
  • Warnings and error codes
    • Errors
    • Error codes
      • HTTP response status codes
      • Error format for Shopper APIs
      • Error codes for Shopper APIs
        • 400 Bad Request
        • 401 Unauthorized
        • 403 Forbidden
        • 404 Not Found
        • 405 Method Not Allowed
        • 409 Conflict
        • 412 Precondition Failed
        • 413 Payload Too Large
        • 500 Internal Server Error
      • Error format for Admin APIs
        • Async error objects
        • Sync error objects
        • Deployment objects
        • Warning objects
      • Error codes for Admin APIs
        • Error patterns
        • Supported image types
        • Asynchronous response error codes
        • Deployment error codes
        • Synchronous response error codes
  • Commerce API reference guide
    • API structure
      • API keys
      • Supported OAuth and Commerce API formats
      • Mini cart widget
      • Custom attributes
      • Fields used as keys
      • Fields and expand query parameters
      • Caching responses
      • CORS support
      • JSONP support
      • Transport
      • Service profiles
      • Supported protocols and formats
      • Elements
      • Rate limiting
      • Locale and currency
      • Exchange rate
      • Product identifier
      • Product external reference identifier (ERID)
      • Customer external reference identifier ERID
      • Cancel request process
      • Failover and redundancy
      • Troubleshooting API calls
    • Shopper APIs reference
      • Carts
        • Offers
          • Offer types
          • POP offers
          • Applied offers
          • Eligible offers
      • Orders
      • Returns
      • Links
    • Admin APIs reference
      • Subscriptions
      • Sites
      • Products
      • Live changes
      • Authorized shipping and billing countries
      • Merchandising
      • Disclosures
    • Glossary
Powered by GitBook
On this page
  1. Warnings and error codes
  2. Error codes

Error codes for Shopper APIs

Understand the internal error codes for the Shopper APIs.

PreviousError format for Shopper APIsNext400 Bad Request

Last updated 5 months ago

When integrating with our Shopper APIs, it's essential to understand the responses you receive, especially when something doesn't go as planned. This section provides an overview of the common error codes you might encounter using our APIs. Understanding these codes allows you to troubleshoot issues more effectively and implement robust application error handling. Whether it's a client-side error indicating a problem with the request or a server-side error pointing to an issue on our end, this guide will help you navigate and resolve any discrepancies efficiently.

Significance of Error Codes

Error codes are critical in understanding the issues that occur during API integration. They serve as immediate indicators of what went wrong in the interaction between the client application and the server:

  • : Indicates that the server cannot process the request due to a client error, such as incorrect syntax.

  • : This error code signals the request lacks valid authentication credentials.

  • : This error code means access to the requested resource is denied, possibly due to insufficient permissions.

  • : The requested resource was unavailable on the server.

  • : Occurs when the resource does not support the method specified in the request.

  • : Suggests a request conflict with the server's current state.

  • : Indicates that one or more conditions given in the request header fields are evaluated as false when tested on the server.

  • : This error code means the request is larger than the server can process.

  • : Signals a generic error message when the server encounters an unexpected condition and no more specific message is suitable.

Understanding these codes helps developers diagnose problems quickly, making it easier to implement solutions or contact support with a clear understanding of the issue.

400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
405 Method Not Allowed
409 Conflict
412 Precondition Failed
413 Request Entity Too Large
500 Internal Server Error