APIs are only as good as the data they return, and keeping them reliable means constantly adapting to changes on the web. Source websites redesign their pages, shuffle their markup, and tweak how information is rendered, often without warning, and every one of those changes can quietly break a scraper that was working perfectly the day before. Staying ahead of that means watching our APIs closely, catching breakages fast, and shipping fixes before they cost you data quality.

This week, we resolved two scraper disruptions that were silently limiting the data our APIs returned, and we shipped a set of new response fields on our Amazon Product API to give you a fuller picture of every listing. None of these changes require any action on your part, they're live now, and your existing integrations will simply start returning better data. Here's a closer look at everything that changed, why it happened, and what it means for the applications built on top of these APIs.

Google Scholar periodically restructures the underlying page markup on its author profiles, and one such change tripped up our parsing logic. As a result, the Google Scholar Author API was incorrectly returning only a single article for each author, no matter how many publications actually appeared on their profile. If you were pulling an author's full publication history, for citation tracking, academic research tools, or building out researcher profiles, this meant your results were badly incomplete.

We've since rewritten the parsing logic to correctly handle Google Scholar's current page structure. The API now correctly returns all available articles associated with an author's profile, so your publication lists are complete again. If you noticed truncated results over the past few weeks, this fix should resolve it automatically on your next request, no changes needed on your end.

Beyond fixing what was broken, we're also investing in giving you richer data out of the box. The Amazon Product API has been enhanced with three new response fields, all aimed at making product data easier to work with and more useful for downstream applications like price trackers, comparison tools, and catalog enrichment pipelines:

●  product_highlights – the key selling points pulled directly from the listing, so you don't have to scrape and parse bullet points yourself

●   full_title – the complete, untruncated product title, useful anywhere a shortened title isn't descriptive enough

●  buybox_unqualified – a flag indicating whether the current Buy Box winner is marked as unqualified, which matters for anyone tracking seller eligibility or pricing competitiveness

Together, these additions make it easier to display detailed product descriptions without extra parsing, work with the full product title instead of a truncated version, and quickly assess Buy Box eligibility without a separate lookup. All three fields are available now in the standard API response, no new parameters or endpoint changes required.

Similar to the Google Scholar issue, changes to eBay's page structure and underlying tags caused the eBay Product API to miss UPC codes for a subset of products. UPC codes are a small but important field for anyone matching listings against internal catalogs, deduplicating products across marketplaces, or feeding data into inventory systems that key off standardized product identifiers, so a gap here could ripple through an entire pipeline.

We've updated the extraction logic to support eBay's latest markup, and UPC code retrieval is now fully restored across affected listings. As with the Google Scholar fix, this is a backend change, you'll see complete UPC data on your next call without needing to update any integration code.

We're continuing to expand response coverage across our product and academic data APIs, with more field additions and structural improvements planned for the coming weeks. If there's a field you wish an API returned, or a piece of data you're currently having to scrape or compute yourself, we want to hear about it, since requests like these are exactly what shaped this week's Amazon Product API additions. 

That's it for this week. Web scraping is a constantly moving target, and keeping our APIs accurate means staying on top of every markup change our source sites make. If you run into any issues, notice missing data, or have requests for new fields, reach out to our support team, we're always working to keep your data accurate, complete, and reliable.