Postalcode was seen to be masked since yesterday for FindingService API for operation-name findItemsAdvanced. The postalcode was seen as-is before. Any means of getting the as-is postalcode through eBay FindingService API ?
I've also seen this issue recently when using the ebay API.
Most annoyingly It seems ebay have changed their policy for sharing presale information - possibly due to their interpretation of data protection.
The issue is discussed with reference to the ebay UI here: https://community.ebay.co.uk/t5/Buyer-Central/Buyers-can-no-longer-see-sellers-postcode-on-any-item-WHY/td-p/6249678
Related
I am developing a web app for client requirement in that i am using Google API for finding nearby place
https://maps.googleapis.com/maps/api/place/nearbysearch/json?location=.....
I was able to get all the required details. Name, rating, etc but only description is missing. will i be able to get it from anywhere, i tried
https://maps.googleapis.com/maps/api/place/textsearch/json?query=...
but not getting required result only country or place is getting here not restaurant or venue description. Please help me to get details for each item in nearby search result. Or any other suggestions
Based on the documentation of both Google Places API Nearby Search Requests and Google Places API Text Search Requests, description property is not included in the returned results. You could rather file for a Feature Request to include description to each returned places in the results here at Google Public Issue Tracker.
Issue Tracker is a tool used internally at Google to track bugs and
feature requests during product development. It is available outside
of Google for use by external public and partner users who need to
collaborate with Google teams on specific projects.
You can learn more about Issue Tracker through this link.
I would also like to suggest to read Google Places API Place Details. It returns more comprehensive information about the indicated place such as its complete address, phone number, user rating and reviews.
Hope this help!
So, I stepped once at this problem. I had offered a website that used the SoundCloud API. Everything worked properly. Content was extracted from the JSON and placed in the layout of the website. However, I received an email one day from the owner of the website, which indicated that the website did not work properly. I then came out to investigate and came to the conclusion that the "problem" was not on my side, but at SoundCloud's side. I studied on the API page of SoundCloud and came to the conclusion that the API had received a major update, making the link with SC and the site no longer worked.
Lately I'm trying many new APIs to, including those from Instagram and Dribbble. I was therefore wondering if it is at all possible to ensure that such problems can be reduced in the future or it might be appropriate API pages of this third-party APIs to monitor?
There's no "right" answer. After many years of using and maintaining many APIs here are some of the conclusions I've come to:
The best providers let you work with a specific version of their API whose interface and expected behavior never changes. They might release bug fixes and new endpoints, but you can be confident that as long as the API is supported it will not break your system.
A good provider will provide an end-of-life date for each version of their API. It's up to you to keep track of when you need to update.
Paid services will often be supported longer than free services. Plus the contract / SLA will guarantee it remains available for a specific amount of time.
The most popular APIs often have mailing lists and/or blogs. For those that offer it, sign up to be notified of updates. For those that don't you'll have to monitor their blogs or news posts. And I suggest not using any service that would drop support for an API version without warning.
I built a module for my company's marketing team to fetch all the photos based on a hashtag. Such as #nofilter.
I was using the URL https://api.instagram.com/v1/tags/nofilter/media/recent with no problems until Instagram decided to change their API authentication to OAuth.
I followed the new guidelines but my client is still in sandbox mode and the API call doesn't return anything anymore. All it returns is:
{"pagination": {"deprecation_warning": "next_max_id and min_id are deprecated for this endpoint; use min_tag_id and max_tag_id instead"}, "meta": {"code": 200}, "data": []}
It seems like I need to submit my application to be reviewed before going live. But this doesn't seem possible, based on what i found from their submission guideline below. Is there any workaround for this?
====== UPDATE July 8th, 2016
I have found one of those 3rd parties that instagram mentioned, but the pricing is awful https://www.dialogfeed.com/pricing/
189 euros per month seem a bit steep
I had to deal with this. Their documentation is pretty unhelpful and doesn't seem to offer any solution for someone just wanting to collect relevant links, which should be no prob.
Fortunately, the script on an Instagram page provides easy access to their structured data. In my rails app I create a headless browser and just hit their url. I provided my solution as an answer to another question:
https://stackoverflow.com/a/38572893/4888422
Is it possible to retrieve shipping quotes on the fly through an external API when a user purchases something through my eBay store?
eBay (and previously PayPal) does not expose the shipping quotes API for various reasons (including technical, business, and pricing reasons) so the short answer is "no, there is no way". In fact it gets the quotes from an external (independent) source.
You can try integrating with Pitney Bowes or a similar provider to get the shipping quotes but that solution is for large players.
UPDATE: Since your company is the one hosting the quote service...
When a user purchaes an item on ebay a "purchase notification" is sent out to a merchant. There are a few different versions of it which you can read about on eBay's dev site. One of them is ItemSold Notification that you can use.
UPDATE 2:
If I understand you correctly you are trying to inject some business logic into eBay's purchasing UI? I'm afraid you are out of luck here. You have limited (pretty much none) influence on the eBay's web flow.
I used the pincode (400036) in the geocoding webservice, but got a location in China. The webservice is shared below.
http://maps.google.com/maps/api/geocode/json?address=india&components=postal_code:400036&sensor=false
Ideally it should be a location in Mumbai (Bombay) in the state of Maharashtra, India.
Any ideas why this could occur?
Also, any other parameters that can be passed to make this particular pin code work?
Thanks and regards,
Anand
P.S.: I'm a Business Analyst, so my technical know-how and command of programming languages is pretty limited. However, I'll be most happy to receive help from the community here and pass it on to my dev team. Thanks.
Geocoding and working with real-world data is hard, and not even the great Google (no sarcasm, I'm a fan) gets it right all the time. Apparently there is a software or data bug in the Google API, since this works (added Country India to the component filter):
http://maps.google.com/maps/api/geocode/json?components=postal_code:400001%7Ccountry:IN&sensor=false
But this does not, and is not even filtering by country because it still returns Chinese results:
http://maps.google.com/maps/api/geocode/json?components=postal_code:400036%7Ccountry:IN&sensor=false
If you're a paying customer, you can contact Google for support here: http://www.google.com/enterprise/portal
You can use http://geoanalyzer.in for this. Google maps and google api are slighly different as Google Maps shows you results from both Google Maps API and also from Google places hence a lot of time you get wrong data in case of Google Maps API. Geo Analyzer solved this and has been built specifically for Indian addresses.
This is one of the few available solutions that is targeted for Indian address system complexity. I hope this will help.