# ScrapingBee extract_rules must be a JSON string, not a dict

## TL;DR

For dynamic pages use js_scenario, the scenario DSL that supports waiting for selectors, clicking, and scrolling before the response is captured. A typical scenario waits for an element, clicks a button, and scrolls to load more content. For structured data, pass extract_rules as a JSON string in the query, not as a dict; the SDK sends it raw and the API parses it, so passing a dict object fails silently or errors.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Set wait_browser if the page needs extra settle time, and block resources you do not need (images, CSS) to cut cost. Check the raw response before trusting extraction: a 200 with an empty body usually means the selector never matched.

Context: Web (scrapingbee-python README): documents the js_scenario and extract_rules conventions that trip SDK users: the scenario DSL drives wait_for/click/scroll for dynamic pages, and extract_rules must be a JSON string passed in the query.
