Skip to main content
Use POST /web/scrape with formats.parse: true, parseParams.type: "prebuilt", and one parser name per request. Don’t send custom rules. See the Quickstart for authentication and SDK setup.

​
Read the output

The parsed output identifies the parser in parsed.type. Check parsed.success before reading parsed.data; each parser’s page documents its data fields. A failed parse has data: null, with an error_code and message, and can coexist with successful outputs in the same request. See timeouts and errors.

​
Page content and browser profiles

Emails, phone numbers, and links use page HTML after content filtering. They support browser actions and browser profiles. They extract from one page rather than crawling a site. Google Maps and app store parsers fetch source data separately, using a US exit. Content filters and browser actions do not change those parser results, and browser profiles are unsupported. Google Play’s hl and gl query parameters and the App Store’s country path still select the source locale or storefront. Caching, timeouts, and zero data retention apply to all parsers. Use the Custom parser for CSS rules or JSON extraction for a schema you define.