Scrapingdog Weekly Changelog: Aug 24-30, 2026

The Post Scraper API has received a significant upgrade this week. Previously, developers pulling post data through the API would receive only the core text and metadata fields, requiring a separate call or manual workaround to retrieve any associated links or images referenced in a post. That limitation has now been removed. The API response has been expanded to include links and image content directly within the standard payload, giving users a single, unified response that captures the full context of a post in one request.

This update is particularly useful for teams building content aggregation tools, social listening dashboards, or media archiving systems, where visual and reference context matters as much as the text itself. Instead of stitching together multiple API calls or writing custom parsing logic to backfill missing media, developers can now rely on the Post Scraper API to deliver a complete picture out of the box. This reduces integration complexity, cuts down on the number of requests needed per post, and ultimately speeds up how quickly applications can process and display scraped content. Existing integrations are unaffected and will simply start receiving the additional fields where available.

Several users reported that the Flipkart Search API was intermittently returning empty result sets for search queries that should have returned valid product data. After investigation, the issue was traced back to a problem in how search data was being retrieved and processed on the backend, which in certain conditions caused legitimate queries to come back with no results at all rather than falling back or erroring out clearly.

This has now been fully resolved. The underlying data retrieval logic has been corrected, and the Flipkart Search API is once again returning accurate, complete search results consistently across all supported query types. This fix directly improves the reliability of any workflow that depends on Flipkart search data, whether that's price monitoring, product research, competitive analysis, or catalog enrichment. Users who may have implemented temporary workarounds — such as retry logic or fallback caching to compensate for the empty-result issue can now safely remove those workarounds, as the API is expected to behave predictably going forward. We appreciate the reports from users who flagged this issue, which helped us identify and resolve it quickly.

Up until this week, teams on the platform were capped at a maximum of 10 members, which meant that larger organizations or fast-growing teams eventually hit a hard wall when trying to bring more collaborators into their workspace. This restriction has now been lifted entirely. Teams can add as many members as they need, with no upper limit on team size.

This change is aimed at making the platform more accommodating for larger organizations, agencies, and enterprises that rely on broader collaboration across departments or client accounts. Team admins no longer need to plan around the old ceiling, remove inactive members to make room for new ones, or split large teams into smaller sub-groups just to stay under the limit. This should make account management simpler and more flexible, particularly for customers who are scaling up their usage of the platform or consolidating multiple smaller teams into one larger, unified workspace.

A notable pricing change has also gone into effect for Amazon scraping requests. Previously, scraping Amazon data from non-US country domains was priced at 5 credits per request, significantly more expensive than scraping US-based Amazon data. That pricing gap has now been eliminated. Amazon scraping is priced at just 1 credit per request across all supported countries, regardless of region.

This represents an 80% cost reduction for any workflow that relies on non-US Amazon data, including international price tracking, cross-border competitor monitoring, and global catalog research. Users who previously limited their scraping scope to US-only data due to cost constraints can now expand their coverage to additional Amazon marketplaces without a significant increase in credit spend. This update is applied automatically, so no changes are required to existing integrations; the reduced pricing takes effect immediately on all qualifying requests.

Taken together, this week's updates strengthen the platform across three key areas: richer data, greater reliability, and improved accessibility. The Post Scraper API now delivers more complete post data in a single call by including links and images. The Flipkart Search API has been restored to full reliability after resolving an empty-results bug that was affecting search accuracy. Team collaboration has been made easier with the removal of the 10-member cap, allowing organizations of any size to build out their teams freely. Finally, the pricing update for non-US Amazon scraping makes global data collection significantly more affordable, opening the door to broader use cases for teams operating across multiple regions. Collectively, these changes reflect an ongoing effort to make the platform more powerful, dependable, and cost-effective for all users, whether they're scraping data at small scale or running large, distributed workflows across many markets.