Scrapeless Weekly Changelog: July 20–26, 2026 Updates

TL;DR:

• ChatGPT Scraper now supports optional raw Server-Sent Events data through the new raw_sse request parameter and sse_data response field.
• Amazon Scraper was optimized to improve request success without requiring integration changes.
• Grok Scraper no longer returns an empty payload in the fixed scenario, improving successful result delivery.
• The Alexa Scraper repository is now public with examples in Python, Node.js, Go, Java, and PHP.
• The legacy scraper.shopeev2 and scraper.shopeev3 actors have been retired.

Here’s what shipped at Scrapeless during the week of July 20–26, 2026: raw ChatGPT stream access, a new Alexa developer repository, reliability improvements across Amazon and Grok, stronger service monitoring, and a Shopee actor retirement notice.

🌟 Top Updates

ChatGPT Scraper Adds Raw SSE Output

ChatGPT Scraper can now return the raw Server-Sent Events stream behind a response. This gives teams access to the event-level data alongside the existing structured result.

Two fields were added:

• raw_sse — an optional boolean request parameter. Set it to true to request the raw SSE data.
• sse_data — a string response field containing the SSE data when raw output is requested.

The new output is useful for teams that need to archive the original stream, inspect event sequences, build custom parsers, or compare the raw transport data with the normalized response.

Existing integrations remain compatible because raw SSE output is opt-in. Requests that do not enable raw_sse continue to use the standard response flow.

Amazon Scraper Success Rate Improved

We optimized scraper.amazon to improve request success. The update strengthens the existing actor without changing its integration surface, so current request workflows can continue unchanged.

Grok Empty-Response Issue Fixed

We fixed a case in which scraper.grok could return an empty result. The correction improves successful result delivery for workflows that collect Grok answers for monitoring, analysis, and downstream automation.

🆕 New Alexa Scraper Repository

The official Alexa Scraper repository is now public. It shows developers how to collect structured Amazon Alexa answers through Scrapeless LLM Chat Scraper using the scraper.alexa actor.

The returned data can include Markdown and plain-text answers, citations, source links, follow-up suggestions, and shopping product cards. This supports GEO monitoring, source analysis, regional answer comparison, product-recommendation research, and automated AI-answer pipelines.

The repository includes ready-to-adapt examples in:

• Python
• Node.js
• Go
• Java
• PHP

⬆️ Service Improvements

Stronger Operational Monitoring

We expanded service monitoring so errors can be detected earlier and surfaced for manual intervention. This shortens the path from identifying a service issue to starting operational review and remediation.

📍 Maintenance and Compatibility Notice

The legacy scraper.shopeev2 and scraper.shopeev3 actors have been retired. Calls to either actor now return:

{
  "code": 15002,
  "message": "This actor is no longer supported. If you have any questions, please contact our support team."
}

This is a breaking change for integrations that still reference either retired actor. Review actor names in scheduled jobs, SDK wrappers, and stored request templates. Contact the Scrapeless support team if you need help updating an affected workflow.

👀 What This Means for Developers

This week’s updates provide deeper ChatGPT response access, more reliable Amazon and Grok collection, and a public starting point for Alexa data workflows. Stronger monitoring and the updated ChatGPT collection strategy also improve day-to-day service operations.

Explore the Scrapeless LLM Chat Scraper, review pricing, or read the previous Weekly Changelog.