--
You received this message because you are subscribed to the Google Groups "Google Content API for Shopping" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-content-api-fo...@googlegroups.com.
To post to this group, send email to google-content-...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-content-api-for-shopping.
For more options, visit https://groups.google.com/d/optout.
Hi Murugan,Before looking at any problems under the productstatuses resource you want to review the items under datafeedstatuses and accountstatuses resources. These give the summary information you see under a data feed in the GMC dashboard and the info under the diagnostic screen. My approach if i'm reviewing problems is to clear these two first.
On Thu, Feb 19, 2015 at 1:26 PM, Murugan <skymu...@gmail.com> wrote:
Can any API devs reply to this post? ie should get only inactive/disapproved products. is there any possibilities for this in content api for shopping v2?i have 100k+ products for couple of clients. to get inactive products, i need to get all products status and check the approval status. when try to get 100 products per page through api call, it return the "503 service unavailable" error after some mins,exception 'Google_Service_Exception' with message 'Error calling GET https://www.googleapis.com/content/v2/[MERCHANT-ID]/productstatuses?pageToken=86cb6313cd2b36d2&maxResults=100: (503) Backend Error' in /var/www/[PROJECT-FOLDER]/api-google/src/Google/Http/REST.php:111
On Wednesday, February 18, 2015 at 6:21:48 PM UTC+5:30, Murugan wrote:To find disapproved products, i need to get all products through paging. Is there any possibilities to get inactive/disapprove products?
--
You received this message because you are subscribed to the Google Groups "Google Content API for Shopping" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-content-api-for-shopping+unsubscribe@googlegroups.com.
To post to this group, send email to google-content-api-for-shop...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-content-api-for-shopping.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Content API for Shopping" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-content-api-for-shopping+unsubscribe@googlegroups.com.
To post to this group, send email to google-content-api-for-shop...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-content-api-for-shopping.
To unsubscribe from this group and stop receiving emails from it, send an email to google-content-api-fo...@googlegroups.com.
To post to this group, send email to google-content-api-for-shop...@googlegroups.com.
Hello,
My name is James and I’m from the Content API Team. Thank you for getting back to us.
Allow me to follow up and file a feature request to the rest of the team to see if this kind of functionality is feasible to have on the latest version of API v2.1. For any updates on this, rest assured that someone from our team will keep you posted. Also, you may check out our blog.
Regards,
|
||||||
It's been 6 years since this feature was requested. To get a list of 100K products just to find 2-3 disapproved ones does not make much sense? Disapprovals and warnings happen everyday and as your policies are becoming tighter by the day. It would be fair to let us make a call for these 2-3 products, fix whatever is wrong with them and update the feed.I took a quick look at the blog... you are now letting folks now update the account's phone number and address using the API. This presumably should only happen once, while getting a list of product disapprovals and warnings happens every day. Please bring this to the attention of your priority czar.thanks, A Grocer
|
|
Hello,
We appreciate your patience on this matter. I would like to inform you that this is something that we will support in the future and we already design a plan for this. However, there’s no definite timeline on when this functionality will be implemented and available within the API. Having said that, you may keep an eye on our blog for any updates.
Hoping for your understanding.
Regards,
|
|