Web Browser Extract API

A focused use case

Let a user select an approved page for a narrow extraction task, then display a reviewed record without collecting unrelated browsing history.

A practical workflow

Decide whether the work belongs in the page, an explicitly permissioned extension, or a backend worker. Limit the requested source, define the output schema, and make any transfer of page content visible to the user.

An example record contract

These fields illustrate the decisions to make before implementation. Adapt the names and required values to the receiving system; the table is not a promise of a live endpoint or a provider-specific response.

Limits worth keeping visible

A normal page cannot read arbitrary cross-origin responses. Using no-cors does not expose an opaque response body to page JavaScript.

Before increasing the workload

Run a small, authorized test set through the whole path, including the receiving application. Keep accepted, rejected, and incomplete outcomes distinguishable. A result should retain the context needed to explain its meaning after it leaves the extractor.

Continue with Website Extract API: From HTML to Useful Records for the full implementation discussion, and use the sample contract documentation to review the shape of a handoff.