Web Scraping API for
Clean Markdown & JSON
Retrieve webpage content as Markdown or structured JSON for your application. Choose output formats and extraction fields, then check content and billing for your workload. Start with 1,000 one-time signup credits.
Web Content, Ready to Process.
A web scraping API retrieves a page and returns the content your application requests. Use Markdown for reading or RAG, HTML for your own parser, or an extraction schema for fields such as a product title, price and availability.
For structured JSON, configure extract with a prompt and schema, then read data.extract. Missing or inaccessible source fields need validation; requesting a field does not guarantee that the page contains it.
Need marketplace-specific data? Explore product data APIs. For browser-heavy pages, read the JavaScript scraping guide and compare supported options.
From URL to Structured Data.
Request Markdown and a structured title from a public page. The response below is illustrative; inspect the actual output and errors for your target.
curl -X POST "https://api.datablue.dev/v1/scrape" \
-H "Authorization: Bearer wh_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","formats":["markdown"],"extract":{"prompt":"Extract the page title","schema":{"type":"object","properties":{"title":{"type":"string"}}}}}'{
"success": true,
"data": {
"markdown": "# Example Domain",
"extract": {
"title": "Example Domain"
},
"metadata": {
"title": "Example Domain",
"status_code": 200
}
}
}Every Format You Need,
in One Call.
Choose the formats your application consumes. Extraction and browser options can add billed components.
markdown
Page text formatted for reading and downstream processing. Review the output for missing or irrelevant content.
html
HTML output for your own parser. See the reference for available cleanup options.
links
Discovered links from the retrieved content; this is not a complete site inventory.
screenshot
A viewport or full-page image, subject to supported capture options and browser billing.
extract (structured JSON)
A prompt and schema define the requested fields. Read data.extract and validate the values against your source.
metadata
Page metadata, such as title and status code, when available.
Built for Production, Priced for Scale.
Scrape billing is additive. A delivered page, structured extraction, explicit browser work and PDF pages can contribute separate components. Automatic JavaScript fallback alone does not trigger the explicit browser-work component. Review the workload calculator and current billing units before estimating volume.
Use documented wait conditions and actions when the data needs a browser interaction. Compare representative pages, missing fields and error responses before scaling; no retrieval mode guarantees that every target will return usable content.
DataBlue also provides search, commerce, quick-commerce, ads, YouTube and App Store endpoints. Choose the API that matches your output, or follow the MCP setup guide for an AI client. API usage still requires an account and available credits.
What Teams Build With It.
A reliable scrape API quietly powers a surprising amount of software, including RAG pipelines and AI agents.
LLM & RAG ingestion
Retrieve page text as Markdown for a retrieval pipeline. Review content quality before indexing it.
AI agent web access
Connect a compatible AI client through the documented MCP setup to retrieve page content using your DataBlue account.
Structured data extraction
Request product fields or specifications using extract and a schema. Validate the returned values and source coverage.
Content & change monitoring
Re-scrape a page on a schedule and diff the markdown or JSON output. Choose a collection schedule appropriate to your freshness requirements.
Firecrawl migration
Compare request options, response fields and costs, then test representative pages before migrating.
Visual QA & archiving
Capture full-page screenshots alongside markdown or JSON. Keep a visual record of exactly what was scraped and when.
Make Your First Request.
Create an account, generate an API key, and test a representative public page.
Create a Free Account
Start with 1,000 one-time signup credits.
Send Your First Scrape
Call /v1/scrape with a Bearer token and a URL. Choose formats such as Markdown; add extract for schema-guided JSON.
Read the Output
Check success and the returned data. Read data.markdown or data.extract, and validate the fields your application needs.
Scrape credit weights are visible before you run.
Start with 1,000 one-time signup credits. The live pricing catalogue lists each billing component. Estimate your configured output rather than applying one price to every request. Effective subscription dollar costs assume full use of included credits.
Scrape API Questions.
What is a Scrape API?
A web scraping API retrieves content from a URL and returns requested formats such as Markdown, HTML or links. DataBlue is a hosted service; you call the API rather than operate the retrieval infrastructure. Results depend on the target page and requested options.
How do I convert a webpage to Markdown with an API?
Send POST /v1/scrape with a URL and formats: ["markdown"]. Read data.markdown in a successful response. Check the returned content before using it in a RAG pipeline; extraction can omit or retain content depending on the page.
Does the Scrape API handle JavaScript-rendered pages?
DataBlue supports browser retrieval for pages that need JavaScript. Wait conditions and page actions can help with dynamic content, but rendering support does not guarantee access to every site. Validate representative pages and the returned fields.
Can I extract a product title, price and availability as JSON?
Use the extract object with a prompt and JSON Schema alongside formats such as ["markdown"]. Read the structured output from data.extract. Only request fields supported by the source page and validate missing values. For supported marketplaces, compare the dedicated product endpoints in the API directory.
Is this compatible with Firecrawl?
DataBlue has a Firecrawl-shaped scrape surface, but compatibility depends on the options and SDK version used. Compare request fields, response fields, errors and billing; test your integration before switching providers.
What output formats are supported?
The scrape request supports Markdown, HTML, links and screenshots. Structured extraction is configured separately with extract; it is not a "json" formats entry. Metadata accompanies the result. See the API reference for format-specific options.
Can the API click, scroll, or wait before scraping?
Use the documented actions and wait_for options for browser interactions. css_selector, include_tags and exclude_tags control content selection. Explicit browser work can add a billing component; check the current calculator and reference before running it.
How much does the Scrape API cost?
Scrape billing is additive: the delivered page and any billed extraction, explicit browser work or PDF pages contribute separate components. Automatic JavaScript fallback alone does not imply an extra browser component. Use the current pricing catalogue and workload calculator for the configured output; one request is not a universal flat price.
Can I scrape pages that need a mobile viewport?
Set mobile: true for mobile emulation. mobile_device is a documented device-name string, not a boolean. Target websites may return different content for different viewports; validate the output you need.
What happens if a page fails to load or blocks scraping?
Inspect success, status and error fields before consuming a response. The published scrape billing policy releases credits for failed work and bills delivered components. A successful HTTP response alone does not prove the requested content was delivered.
Start Scraping in JSON.
Test Markdown or structured extraction against a representative page. Start with 1,000 one-time signup credits.

