ScraperFly is built to keep the API surface understandable: clear request parameters, clear response formats, clear billing behavior, and clear documentation.
If a product behavior, API option, pricing detail, documentation path, or operational note changes in a way customers should know about, we will record it here.
Current status
The first public version focuses on core request workflows: fetching public pages, choosing response formats, enabling rendering when needed, testing request controls, and using flexible credit-based billing.
What we will publish here
Small copy edits and routine documentation cleanup may not appear here. Changes that affect usage decisions will.
- New API parameters or behavior changes.
- Documentation updates that affect implementation.
- Billing, credit, or plan changes.
- Status and reliability notes when they affect customers.
- Important product improvements that change how teams use ScraperFly.