WS WebScraperStudio Public content layer for scraping buyers
Home/Docs/Developers/API Boundary

Developers

API Boundary

Updated July 1, 2026 This document explains which parts of WebScraperStudio are public contract and which remain server-only.

Public Contract

The public contract is intentionally narrow: template metadata, safe demo runs, diagnostics submission, contact lead submission, and the backend webhook that keeps provider jobs in sync.

Server-Only State

Provider credentials, admin sessions, provider collection identifiers, and protected operational state remain server-only. The public content layer can link to actions that use those contracts, but it never exposes the underlying secrets or open-ended controls.

Why the Boundary Matters

As the site grows into a content platform, the boundary matters more, not less. Broader content should increase traffic and decision support without widening the unsafe parts of the product surface.

Next action

This document explains which parts of WebScraperStudio are public contract and which remain server-only.

Inspect public template API Escalate a scoped request

Frequently asked questions

Should docs pages call provider APIs directly?

No. All provider access stays behind the site's own backend contracts.

Does the public site change the backend API shape?

Not in phase one. The content layer is new, but the backend contracts stay stable.

Related guides

Developers

Scraper API vs Scraper Studio

Choose between prebuilt dataset routes and custom collector workflows based on scope, control, and support overhead.

Getting Started

WebScraperStudio Overview

Understand how the public content layer, scraper catalog, and diagnostics workflow fit together.

Continue with

Ecommerce

Amazon Product Monitor

The safest public Bright Data demo: one product URL in, a truncated product preview out.