MH MediaHarvester Web Context API

HTML

Scrape HTML

Fetch rendered or raw HTML when developers need the DOM itself.

GET /v1/web/scrape/html

What you get

Developer-ready output for Scrape HTML

01 Raw HTML output
02 Optional iframe capture
03 PDF parsing controls
04 Timeout and wait controls

How it works

Four steps from request to usable JSON

1

Send the target URL

2

Fetch fast HTML first

3

Escalate if render is needed

4

Return HTML with status metadata

API response

Fields developers usually wire first

Extract HTML from any accessible URL, including page frames when requested.

html url final_url meta.engine
curl.exe -H "X-API-Key: mh-localhost-dev-key" "http://127.0.0.1:8013/v1/web/scrape/html"

Developer FAQ

Common questions about Scrape HTML

12 answers
When should I use HTML instead of Markdown?

Use HTML when you need exact DOM structure, attributes, scripts, data layers or your own parser. Use Markdown when an LLM needs readable page content.

Can it include iframe content?

Yes. Set includeFrames when iframe content matters. The response marks frame URLs separately so your parser can decide how to use them.

Does it execute JavaScript?

The router starts with a fast fetch and escalates to browser-style engines when quality is low or the page needs rendering.

What endpoint should I call for Scrape HTML?

Use GET /v1/web/scrape/html. Local development accepts the X-API-Key header with mh-localhost-dev-key, and production clients can use the same shape with their own key.

Can I call it from CLI, SDK, MCP and no-code tools?

Yes. The same endpoint can be called with curl, the TypeScript SDK, Python SDK, MCP server, Zapier, Make, n8n, Google Sheets or Excel workflows where appropriate.

How does caching with maxAgeMs work?

When maxAgeMs is supported, a cached response can be reused if it is younger than the requested freshness window. Set maxAgeMs to 0 when you need a fresh scrape or extraction.

What happens when a page is blocked or requires login?

The API returns clear states such as blocked, verification_required, login_required, robots_disallowed or permission_required. It does not promise to bypass access controls.

Which response fields should I store?

Most integrations store html, url, final_url, meta.engine, plus source URL, status, confidence and timestamp fields when present. Keep source metadata so users can audit values later.

Can I batch this endpoint?

For local or small workflows, loop over a list of URLs or domains. For larger jobs, use crawl, batch workflow endpoints or a queue so failures and retries are tracked cleanly.

How should I handle errors in production?

Check success, HTTP status, error.type and retryable flags. Retry timeouts and temporary network failures, but do not retry robots, login or permission errors without changing input or authorization.

Does the API work with JavaScript-heavy sites?

The engine router starts with fast fetching and escalates when content quality is low. Browser-style rendering is used where available, while access-control barriers are reported explicitly.

Is this safe to use with customer data?

Send only domains, URLs or fields your workflow needs. Use retention controls for generated artifacts and avoid storing unnecessary raw HTML, screenshots or extracted personal data.

Related data APIs

Build the next step in the workflow