This section provides you the list of expected HTTP response error codes while making the API calls to Walmart Connect Sponsored Search Advertising APIs.
Status Codes and Errors
| Code | Description | Notes |
| 200 | OK | The request was successful |
| 400 | Bad Request | The request was not properly formed and therefore was not successful |
| 422 | Unprocessable Entity | The server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions |
| 403 | Unauthorized | Invalid credentials |
| 404 | Entity Not Found | Entity not found. (e.g. This exception will show up when wrong campaign ID is provided) |
| 429 | Too Many Requests | Number of requests have exceeded the calls per hour limit for the endpoint (Rate limit) for the integrator. Retry after 10 minutes. |
| 500/520 | Internal Server Error | An internal server error has occurred |
| 503 | Service Not Available | Server is temporarily unable to handle the request. Try again later |
| 521 | Service Not Available | The origin server has refused the connection. Try again later |
Rate limits on API operations
There is a rate limit in place on the allowed number of API operations per hour.
Operations per hour are computed as the sum of number of changes requested across all API requests during the hour.
For example, 5 keyword bid changes, creation of an ad group, adding an item, and a snapshot report request in any given hour, would be counted as 8 operations.
You will receive an HTTP 429 status error code and an error message about rule enforced in case of breaking ops limit.
To learn more about current applicable limits specific to your integration, please reach out to the API Partner Operations team.