If you build anything on top of search or maps data, you know how frustrating it is when an API that worked yesterday suddenly starts sending back empty results. That's exactly what happened recently with a couple of widely used APIs and the good news is, it's fixed. This week also brought a small but handy upgrade to how search results are enriched. Here's a rundown of everything that changed.
1. eBay Search API: Empty Results Are Gone
For a while, some eBay search requests were coming back with nothing in them, no listings, no prices, just an empty response, even though the search itself was valid. The root cause was that eBay had quietly changed the structure of its search results pages. The API's parser, which is the part of the system that reads eBay's page and pulls out the useful information, wasn't built to recognize the new layout, so it had nothing to extract.
The fix was to rebuild that parsing logic so it correctly understands eBay's current page structure. Every supported eBay search URL now consistently returns full, complete results again. If you had workarounds in place, like retry loops or fallback logic to handle empty responses, you should be able to simplify or remove them.
2. Google Search API: Empty Responses Fixed Too
The Google Search API ran into a very similar problem, and for the same underlying reason: Google updated the structure of its search results pages, and the existing parser couldn't keep up. The practical effect was the same as with eBay, requests that should have returned rich results were instead coming back empty.
This has now been resolved. The parsing logic has been updated to match Google's new page structure, and the API is back to reliably returning full, accurate search results. If your application depends on Google search data, whether that's for research tools, price comparison, content discovery, or anything else, this should restore normal behavior without any changes needed on your end.
3. Google Search API: "People Also Ask" Now Links to AI Overviews
This one isn't a bug fix, it's a new feature. The "People Also Ask" section of Google search results is that familiar list of related questions that expand when you click them. Google sometimes attaches an AI-generated overview to these questions, offering a more detailed, synthesized answer instead of just a snippet from one webpage.
The API now surfaces a link to that AI Overview whenever one is available for a "People Also Ask" question. In practice, that means developers can pull richer, more descriptive answers directly through the API instead of only getting a bare question and a short snippet. If you're building anything that summarizes topics, answers user questions, or enriches search content, this gives you an extra, more detailed source to draw from.
4. Google Maps API: Business Hours and Open Status Now Accurate
The last fix concerns two fields in the Google Maps API: open_state, which tells you whether a place is currently open or closed, and hours, which lists its operating hours. Both had been unreliable, sometimes returning incorrect or inconsistent information, which is a real problem if your app is telling users a restaurant is open when it's actually closed.
The underlying parsing logic that reads this information has been corrected, and both fields now return accurate, dependable data. This matters most for apps that help people decide where to go right now, such as store locators, delivery apps, or local recommendation tools, since incorrect open/closed status directly affects the user's experience.
Why These Fixes Matter
Search and maps APIs work by reading the same web pages a person would see in a browser, then extracting the useful pieces of information. That means whenever eBay, Google, or any other site changes how its pages are built, the API's parser has to be updated to keep working. These kinds of issues are usually invisible to end users until something breaks, like a search returning nothing, or a store showing the wrong hours.
All four issues covered here are now resolved, and the new AI Overview links in "People Also Ask" are live as an added bonus. If you were building workarounds for empty responses or unreliable hours data, this is a good time to remove them and let the API do the work directly.
