Scrapeless Weekly Changelog: July 27–August 2, 2026

TL;DR:

• Amazon Rufus through scraper.amazon now supports the Japan region.
• Two new Rufus parameters support product discovery and product-aware follow-up conversations.
• A custom high-volume datacenter proxy actor is now available through assisted configuration.
• Copilot collection received stability and successful-result improvements.
• Web Unlocker proxy parameter compatibility was updated, and scraper.shopee was retired.

Here’s what shipped at Scrapeless during the week of July 27–August 2, 2026: expanded regional coverage for Amazon Rufus, richer product context, more proxy capacity for large workloads, and reliability and maintenance updates across the platform.

🌟 Top Updates

Amazon Rufus Expands to Japan

Amazon Rufus workflows through scraper.amazon now support the Japan region. Teams can use the same Scrapeless workflow to study product questions and AI-assisted shopping experiences in the Japanese market.

This expansion is especially useful for ecommerce research, product discovery analysis, regional recommendation monitoring, and teams comparing Rufus answers across markets.

New Parameters Enable Product-Aware Rufus Workflows

Rufus requests now support two additional parameters:

• is_get_question — a boolean that requests product recommendation questions. It takes effect only when the result includes product data.
• asin — adds an Amazon product ID as the conversation context. Subsequent questions in the conversation are answered in relation to that product.

Together, these parameters make it easier to move from broad product discovery to focused follow-up research. A workflow can collect relevant recommendation questions, set a specific product as context, and continue asking questions without resending the product reference in every prompt.

💫 New Custom Proxy Capacity for High-Volume Workloads

The custom proxy.datacenter.smart actor is now available for customers with substantial proxy usage. It is designed for high-volume workloads that need dedicated capacity planning and configuration.

This actor is provisioned through an assisted setup rather than a self-service switch. Customers interested in using it should contact the Scrapeless team so requirements, capacity, and configuration can be reviewed before activation.

⬆️ Service Improvements

Copilot Reliability Improved

We improved Copilot collection stability and successful-result delivery. The update strengthens ongoing monitoring and data collection workflows without changing the customer-facing request format.

Web Unlocker Proxy Compatibility Updated

Web Unlocker’s proxy parameter handling was adjusted for compatibility with an upstream interface. This maintenance update keeps proxy configuration handling aligned across the service.

📍 Maintenance and Compatibility Notice

The scraper.shopee actor has been retired. This is a breaking change for integrations that still reference the actor.

Review scheduled jobs, SDK wrappers, saved request templates, and internal documentation for scraper.shopee. Contact the Scrapeless support team to confirm the appropriate path for any affected Shopee collection workflow.

👀 What This Means for Developers

This week’s updates open Amazon Rufus research to Japan and add more control over product-centered conversations. High-volume customers also have a new assisted proxy option, while Copilot and Web Unlocker received operational improvements.

Explore the Scrapeless Scraping API, review pricing, or read the previous published Weekly Changelog.