Who can use this feature?Super users and PIM users with Channel subscription module access and who have subscribed to Shopify with valid API credentials.
Available on Accounts with subscription to Channel Subscription module
When syndicating products from PIMworks to Bigcommerce, the response received from the Bigcommerce API endpoint can vary based on the specific request made by PIMworks.
Below, you will find a list of potential HTTP status codes along with their corresponding error messages.
Error Codes | Message | Purpose | Trouble shooting |
400 | Bad Request | Issued when a malformed request was sent. The request could not be completed due to a URL restriction. Check the URL for ports that may conflict with site permissions. | |
401 | Unauthorized | This response is sent when your client failed to provide credentials or its credentials were invalid. | |
403 | Forbidden | Returned when permissions do not allow the operation. | |
404 | Does not exist | The requested entity does not exist. | |
405 | Method Not Allowed | The resource was found, but doesn't support the request method. Issued when either a specific method isn’t yet implemented on a resource, or the resource doesn’t support the method at all. For example, a PUT on /orders is invalid, but a PUT on /orders/{_id_} is valid. | |
406 | Not Acceptable | When the client specifies a response content type in the Accept header that is not supported. | |
409 | Conflict | A change requested by the client is being rejected, due to a condition imposed by the server. The exact reasons for this response will vary from one resource to the next. An example might be attempting to delete a category whose deletion would cause products to be orphaned. | |
413 | Request Entity Too Large | When the client requests too many objects. For example, the limit parameter exceeded the maximum. | |
415 | Unsupported Media Type | Returned due to issues with the Content-Type header. | |
422 | Missing or Invalid Data | The request cannot be processed either because it omitted required fields or because it contained invalid data | |
423 | Locked Status Code | The requested resource is currently locked and unavailable. | |
429 | Too Many Requests | When an OAuth client exceeds the rate limit for API requests to a store. | |
500 | Internal Server Error | When an error has occurred within the API. | |
501 | Not Implemented | When a request method is sent that is not supported by the API (e.g., TRACE, PATCH). | |
503 | Service Unavailable | When the store is “Down for Maintenance,” being upgraded to a new version, or is suspended due to administrative action or a billing issue. | |
507 | Insufficient Storage | When the store has reached a limitation for the resource, according to their BigCommerce plan (e.g., 500-product limit). |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article