API is not longer working with WooCommerce/Wordpress
Budget: $30 – $250 USD
My API with Inventory Source stopped adding new products from this catalog to my website about three weeks ago. Inventory Source said - we are getting an error "Response Code: 200" for the failed products.
We have ruled out the AWS server as they have confirmed Lightsail is functioning properly.
Here is a note from my developer:
In summary we now know AWS is seemingly working fine, Wordpress API is working for some calls, but the "Batch" call is not working (what Inventory Source needs to use to update multiple order statuses at a time).
I still think this requires a specialty in APIs and backend that you may have to hire for. I would pass along to them that it seems from my research the following are worth investigating:
The error received is "404 No route was found matching the URL and request method."
Is the .htaccess file preventing any kind of API call, or converting POST to GET?
Confirm Batch endpoint is out-of-the-box and doesn't require any custom setup or registering via wp-config.php
These are potential paths forward I've found in researching solutions, but ones that only an API engineer or Backend Wordpress engineer would be able to tackle properly.
Three people have tried to fix this with NO success. Please only inquire if you can fix.
We have ruled out the AWS server as they have confirmed Lightsail is functioning properly.
Here is a note from my developer:
In summary we now know AWS is seemingly working fine, Wordpress API is working for some calls, but the "Batch" call is not working (what Inventory Source needs to use to update multiple order statuses at a time).
I still think this requires a specialty in APIs and backend that you may have to hire for. I would pass along to them that it seems from my research the following are worth investigating:
The error received is "404 No route was found matching the URL and request method."
Is the .htaccess file preventing any kind of API call, or converting POST to GET?
Confirm Batch endpoint is out-of-the-box and doesn't require any custom setup or registering via wp-config.php
These are potential paths forward I've found in researching solutions, but ones that only an API engineer or Backend Wordpress engineer would be able to tackle properly.
Three people have tried to fix this with NO success. Please only inquire if you can fix.