# Error codes for Shopper APIs

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:

* [**400 Bad Request**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/400-bad-request.md): Indicates that the server cannot process the request due to a client error, such as incorrect syntax.
* [**401 Unauthorized**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/401-unauthorized.md): This error code signals the request lacks valid authentication credentials.
* [**403 Forbidden**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/403-forbidden.md): This error code means access to the requested resource is denied, possibly due to insufficient permissions.
* [**404 Not Found**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/404-not-found.md): The requested resource was unavailable on the server.
* [**405 Method Not Allowed**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/405-method-not-allowed.md): Occurs when the resource does not support the method specified in the request.
* [**409 Conflict**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/409-conflict.md): Suggests a request conflict with the server's current state.
* [**412 Precondition Failed**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/412-precondition-failed.md): Indicates that one or more conditions given in the request header fields are evaluated as false when tested on the server.
* [**413 Request Entity Too Large**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/413-payload-too-large.md): This error code means the request is larger than the server can process.
* [**500 Internal Server Error**](/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis/500-internal-server-error.md): 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes/error-codes-for-shopper-apis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.